1. Turn off your firewall or do #sudo iptables --list-rules
2. netstat -nlutp to see if ZK is listening on that port
Issue is there is something blocking access to the port.
+1.314.452.2896 (Tel/SMS)
On Thu, Aug 16, 2018 at 8:15 PM, Raghav wrote:
> 1. Ids/Nodes are correct and their is no prob
1. Ids/Nodes are correct and their is no problem,
2. ZooKeeper started on all three nodes within a span of 5 seconds.
3. Our cluster is not on AWS or on any cloud for that matter.
Is there any zookeeper settings that could possibly help in such scenarios ?
Thanks
R
On Thu, Aug 16, 2018 at 6:12
Ensure ids/nodes are correct in zoo.cfg and zookeeper is running on each. Also
any changes to ports being open? If it’s aws, beck security groups. Node 1
cannot talk to the other two nodes.
> On Aug 16, 2018, at 6:02 PM, Raghav wrote:
>
> Hi
>
> Our 3 node Zookeeper ensemble got powered d
Hi
Our 3 node Zookeeper ensemble got powered down, and upon powering up the
zookeeper could get quorum and kept throwing these errors. As a result our
Kafka cluster was unusable. What is the best way to revive ZK cluster in
such situations ? Please suggest.
2018-08-17_00:59:18.87009 2018-08-17 0
Hi Everyone,
I am using Zookeeper C client library and wanted to check if there are any
plans to add vrf support to Zookeeper client library. The client application
may be in a different vrf from zookeeper server and it would be useful to
provide a vrf name when we call zookeeper init so that a
Thank you
On Thu, Aug 2, 2018 at 10:50 AM John Sirois wrote:
> The full ensemble size is still known (5); so operations still take 3
> successful node writes to work.
>
> On Thu, Aug 2, 2018, 11:46 AM rammohan ganapavarapu <
> rammohanga...@gmail.com>
> wrote:
>
> > Hi,
> >
> > Lets say i have 5
