On 2/25/2015 9:03 AM, Benson Margulies wrote: > It's the zkcli options on my mind. zkcli's usage shows me 'bootstrap', > 'upconfig', and uploading a solr.xml. > > When I use upconfig, it might work, but it sure is noise: > > benson@ip-10-111-1-103:/data/solr+rni$ 554331 > [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:9983] WARN > org.apache.zookeeper.server.NIOServerCnxn – caught end of stream > exception > EndOfStreamException: Unable to read additional data from client > sessionid 0x14bc16c5e660003, likely client has closed socket > at > org.apache.zookeeper.server.NIOServerCnxn.doIO(NIOServerCnxn.java:228) > at > org.apache.zookeeper.server.NIOServerCnxnFactory.run(NIOServerCnxnFactory.java:208) > at java.lang.Thread.run(Thread.java:745)
The upconfig command is VERY noisy. A LOT of data is printed whether it's successful or not, and exceptions on a successful upload would actually not surprise me. An issue to reduce the zkcli output to short informational/error messages rather than the full zookeeper client logging is something I'll do soon if someone else doesn't get to it. I had never noticed the bootstrap option to zkcli before ... based on the options shown, I think it's meant to convert an entire non-cloud (and probably non-redundant) Solr installation (all cores currently present in the solr home) to SolrCloud. It's a conversion that would work, but I think it would be very ugly. There's also a bootstrap option for Solr that does this. Thanks, Shawn
