I found how to solve the problem.
After sending a file to be indexed to a replica shard (node2):
curl 'http://node2:8983/solr/update?commit=true' -H 'Content-type:
text/xml' --data-binary 'asdfbig moth'
I can send a "commit" param to the same shard and then it gets updated:
curl 'http://node2:8
Yes, It's happening with the latest version, 4.2.1
Yes, it's easy to reproduce.
It happened using 3 Virtual Machines and also happened using 3 physical
nodes.
Here are the details:
I installed Hortonworks (a Hadoop distribution) in the 3 nodes. That
installs Zookeeper.
I used the "example" dir
On Mon, May 20, 2013 at 4:21 PM, Sebastián Ramírez
wrote:
> When I send an update to a non-leader (replica) shard (B), the updated
> results are reflected in the leader shard (A) and in the other replica
> shard (C), but not in the shard that received the update (B).
I've never seen that before.
Hello,
I'm having a little problem with a test SolrCloud cluster.
I've set up 3 nodes (SolrCores) to use an external Zookeeper. I use 1 shard
and the other 2 SolrCores are being auto-asigned as replicas.
Let's say I have these 3 nodes: the leader shard A, the replica shard B,
and the (other) rep
