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)
On Wed, Feb 25, 2015 at 10:52 AM, Shawn Heisey <apa...@elyograg.org> wrote:
> On 2/25/2015 8:35 AM, Benson Margulies wrote:
>> Do I need a zkcli bootstrap or do I start with upconfig? What port does
>> zkRun put zookeeper on?
>
> I personally would not use bootstrap options. They are only meant to be
> used once, when converting from non-cloud, but many people who use them
> do NOT use them only once -- they include them in their startup scripts
> and use them on every startup. The whole thing becomes extremely
> confusing. I would just use zkcli and the Collections API, so nothing
> ever happens that you don't explicitly request.
>
> I believe that the port for embedded zookeeper (zkRun) is the jetty
> listen port plus 1000, so 9983 if jetty.port is 8983 or not set.
>
> Thanks,
> Shawn
>
