Thanks Flavio.
Would you know why node2 could not receive ACK from the other 2 nodes .
What is the workaround in scenarios like these where in a 3 node cluster 1
node is not responding
** If we do a rolling restart there is a possiblity of a downtime
** Add 2 more nodes to the configs and do a ro
Hi,
I'm new to the Zookeeper community. I've started using Zookeeper a few
months ago.
My current goal is to build a rolling update process for three Zookeeper
nodes running on AWS. During the update the virtual machines get replaced
one by one. A new machine with Zookeeper is launched and added
In the end I think I found the issue: I was using a wrong password to trigger
session expiration. This was probably due to an issue on printing target
ZooKeeper's handle itself which, in turn, led to invoking the code with an
invalid password.
Thanks again for helping!
Matteo
-Messaggio
Hi Flavio,
thanks for replying.
Yes, pretty much sure serviceZKSessionId value corresponds to a valid ZooKeeper
session: on the target ZooKeeper handle side I can see a few log lines upon
running the previous code:
16-04-13-09-15-52 ZK event: WatchedEvent state:Disconnected type:None
path:nu
Are you sure serviceZKSessionId is valid?
-Flavio
> On 13 Apr 2016, at 08:39, Matteo Casadei - Diennea
> wrote:
>
> Hi everybody,
>
> I have an issue on testing ZooKeeper's session expiration.
>
> Basically, I am using the chunk of code below to make a "target"
> ZooKeeper handle expire:
>
Hi everybody,
I have an issue on testing ZooKeeper's session expiration.
Basically, I am using the chunk of code below to make a "target"
ZooKeeper handle expire:
...
final ZooKeeper zk = new ZooKeeper(zkAddress , zkTimeout, new Watcher() {
@Override
pub
