Hello
We are using Solr 8.9.0. We have configured Solr cloud like 2 shards and
each shard has one replica. We have used 5 zoo keepers for Solr cloud.
We have used the below schema field in employee collection.
*Total no of record*: 8562099
*Size of instance:* solrgnrls2r167GB solrgnrls1-
How many docs have you added before the softCommit?
Do you use any cache warming or other commit hooks?
Jan
> 28. sep. 2023 kl. 13:28 skrev John Jackson :
>
> Hello
>
> We are using Solr 8.9.0. We have configured Solr cloud like 2 shards and
> each shard has one replica. We have used 5 zoo keep
How many docs have you added before the softCommit?
>> only one record EMP5487098118986160 added.
Do you use any cache warming or other commit hooks?
>> No we are not using any cache and our commit for solr config below
60
2
false
100}
We are indexing via zoo keeper and do not comm
> 100}
There seems to be a typo here with the "}"?
It is unusual with 100ms commit time, you risk that commits pile up during
rapid indexing and cause inefficiencies. I'd increase it to at least 1000ms.
Can you reproduce this in an IDLE system by simply adding ONE document?
What does your docu
Dear Community
Is there a way to cancel a shard split operation in solr? I couldn’t find any
such option in collection/core management API. I see the operation is tracked
via zookeeper nodes,will I be able to cancel the operation by clearing these
nodes from ZK?
Regards
Hitendra
Scanned this thread, apologies if I missed something, but here's a few
thoughts:
To get better advice make it clear if you are running Solr in Cloud mode
(a.k.a. self managed) or Legacy (a.k.a user managed). Some ways to know
which quickly:
1. Is there an associated Zookeeper cluster? If yes,
Unless you are very experienced and comfortable with solr, do not edit
zookeeper nodes directly. Things you should touch generally have support in
bin/solr or other provided tools. If you edit the wrong things you can
cause all manner of chaos, and even completely ruin the entire cluster,
requiring
