I’m not sure of the root cause for your problem.
Solr is built to stay in sync automatically, so there is no need to script
anything in that regard.
There may be something with your environement, network, ZooKeeper setup or
similar that caused the state you were in. I would need to dig further in
Hi,
I did as you said, now it is coming ok.
And what are the things to look for while checking about these kind of
issues, such as mismatch count, lukerequest not returning all the fields
etc. The doc sync is one, how can I programmatically use the info and
sync them ? Is there any method
Hi,
There is clearly something wrong when your two replicas are not in sync. Could
you go to the “Cloud->Tree” tab of admin UI and look in the overseer queue
whether you find signs of stuck jobs or something?
Btw - what warnings do you see in the logs? Anything repeatedly popping up?
I would al
Hi,
a.) Yes index is static, not updated live. We index new documents over
old documents by this sequesce, deleteall docs, add 10 freshly fetched
from db, after adding all the docs to cloud instance, commit. Commit
happens only once per collection,
b.) I took one shard and below are the result
Could it be that your cluster is not in sync, so that when Solr picks three
nodes, results will vary depending on what replica answers?
A few questions:
a) Is your index static, i.e. not being updated live?
b) Can you try to go directly to the core menu of both replicas for each shard,
and comp
Wire shark should show you what HTTP request actually looks like. So, a
definite reference.
I still recommend double checking that equivalence first. It is just sanity
check before doing any more expensive digging.
You can also enable trace logging in the admin ui to see low level request
details
Hi Alexandre,
I am sure I am firing the same queries with the
same collection everytime.
How do WireShark will help ? I am sorry not experienced with that tool.
On 13/08/16 17:37, Alexandre Rafalovitch wrote:
Are you sure you are issuing the same queries to the same colle
Are you sure you are issuing the same queries to the same collections and
the same request handlers.
I would verify that before all else. Using network sniffers (Wireshark) if
necessary.
Regards,
Alex
On 13 Aug 2016 8:11 PM, "Pranaya Behera" wrote:
Hi,
I am running solr 6.1.0 with solr
Hi,
I am using Java client i.e. SorlJ.
On 13/08/16 16:31, GW wrote:
No offense intended, but you are looking at a problem with your work. You
need to explain what you are doing not what is happening.
If you are trying to use PHP and the latest PECL/PEAR, it does not work so
well. It is con
No offense intended, but you are looking at a problem with your work. You
need to explain what you are doing not what is happening.
If you are trying to use PHP and the latest PECL/PEAR, it does not work so
well. It is considerably older than Solr 6.1.
This was the only issue I ran into with 6.1.
Hi,
I am running solr 6.1.0 with solrcloud. We have 3 instance of
zookeeper and 3 instance of solrcloud. All three of them are active and
up. One collection has 3 shards, each shard has 2 replicas.
Everytime query whether from solrj or admin ui, getting inconsistent
results. e.g.
1. numF
11 matches
Mail list logo
