Hello,

We use solrcloud with two shards (no replication for now), zookeeper is in
a separate machine and it works well until yesterday when I renamed some
cores, cleaned other unused ones that we don't need anymore etc... then I
got tons of these errors when I try to put docs into my core "sellers", so
I can't add docs anymore :

> 10.213.0.124  10.213.0.124    solrcloud-2 POST 
> /solr/Sellers_shard1_replica1/update?update.distrib=TOLEADER&distrib.from=http%3A%2F%2Fsolrcloud-2%3A8080%2Fsolr%2FSellers_shard1_replica1%2F&wt=javabin&version=2
>  HTTP/1.1
>     S 5265 ms 0 KB    0 KB    10.213.0.124    10.213.0.124    solrcloud-2 
> POST 
> /solr/Sellers_shard1_replica1/update?update.distrib=TOLEADER&distrib.from=http%3A%2F%2Fsolrcloud-2%3A8080%2Fsolr%2FSellers_shard1_replica1%2F&wt=javabin&version=2
>  HTTP/1.1
>     S 5253 ms 0 KB    0 KB    10.213.0.124    10.213.0.124    solrcloud-2 
> POST 
> /solr/Sellers_shard1_replica1/update?update.distrib=TOLEADER&distrib.from=http%3A%2F%2Fsolrcloud-2%3A8080%2Fsolr%2FSellers_shard1_replica1%2F&wt=javabin&version=2
>  HTTP/1.1 S  5277 ms 0 KB    0


in zookeeper I see some exceptions :

EndOfStreamException: Unable to read additional data from client
sessionid 0x14b98fd8e860000, likely client has closed socket
        at 
org.apache.zookeeper.server.NIOServerCnxn.doIO(NIOServerCnxn.java:220)
        at 
org.apache.zookeeper.server.NIOServerCnxnFactory.run(NIOServerCnxnFactory.java:208)
        at java.lang.Thread.run(Thread.java:745)

I don't see any relation between deleting some cores and theses errors but
in the admin gui I see the shards list display changed (shard2 have 2
machines?!! it's configured just in one) : [image: enter image description
here]

I sent cores configs to zookeeper using zcli, I reloaded cores, I restarted
tomcat without any result, any advices??

Tomcat 7, Solr 4.10



http://stackoverflow.com/questions/28584066/solrcloud-no-puts-anymore-and-tons-of-updateupdate-distrib-toleader

-- 
Cordialement,
Abdelali AHBIB



-- 
Cordialement,
Abdelali AHBIB

Reply via email to