Hmm, 4.9 is reasonably recent. Do you by chance have the suggester
uncommented?
the suggester rebuilds whenever the core starts, see solrconfig.xml. But
that should
happen on _all_ the shards so I rather doubt this is the problem.
How big are your transaction logs? Look in the .../data/tlog direct
sorry mail list reformat my email
> On Mar 4, 2015, at 13:47, 龚俊衡 wrote:
>
> Hi, Erick
>
> Thanks for you quick replay,
>
> we are using Solr 4.9.0 and use 4 Aliyun cloud instance with 4 core cpu 32G
> mem and 1G SSD
>
> shard distribute as:
>
> we have 4 shard
>
> Node
> shard1_0
>
Hi, Erick
Thanks for you quick replay,
we are using Solr 4.9.0 and use 4 Aliyun cloud instance with 4 core cpu 32G mem
and 1G SSD
shard distribute as:
we have 4 shard
Node
shard1_0
shard1_1
shard2_0
shard2_1
prmsop01 10.173.225.147
E
E
prmsop02 10.173.226.78
E
E
prmsop03 10.173.225.163
It's always important to tell us _what_ version of Solr you are
running. There have
been many improvements in this whole area, perhaps it's already fixed?
Best,
Erick
On Tue, Mar 3, 2015 at 6:20 PM, 龚俊衡 wrote:
> Hi,
>
> I found when a replica recovering, one of cpu core (usually cpu0) will load
Hi,
I found when a replica recovering, one of cpu core (usually cpu0) will load
100%, and then leader update will fail cause this replica can not response
leader’s /update command
this will cause leader send other recovery to this replica then this replica in
a recover loop.
my question is i
Hi, Erick,
I found problem, because we have only one shard on server with heavy update
request (over 250/s) but solr just only use one core of cpu.
> On Mar 2, 2015, at 01:25, Erick Erickson wrote:
>
> Several. One is if your network has trouble and Zookeeper times out a Solr
> node.
>
> Can
Several. One is if your network has trouble and Zookeeper times out a Solr node.
Can you describe your problem though? Or is this just an informational
question? Because I'm quite sure how to respond helpfully here.
Best,
Erick
On Fri, Feb 27, 2015 at 10:37 PM, 龚俊衡 wrote:
> HI,
>
> Our producti
HI,
Our production solr’s replication was offline in some time but both zookeeper
and network is ok, and Solr jvm is normal.
my question are there any other reason will let solr’s replication into
recovering state?
