Awesome.
I wonder if you are expecting to record your talk.
Ivan
On Fri, Sep 14, 2018 at 2:46 AM Mohamed Jeelani wrote:
> Your ZooKeeper friends @ Facebook would like to invite you to share and
> learn what’s new with ZooKeeper.
>
> We will not only share what we at Facebook have been up to,
Andor,
Yes you are right, i miss understood the log message.
Thanks,
Ram
On Fri, Sep 14, 2018 at 3:23 AM Andor Molnar wrote:
> Hi Ram,
>
> I might be missing something from your explanation, but that error message
> alone is not an issue. All ZK nodes open connection to each other, but
>
I have a 3 node cluster on 3.4.12. One of the nodes (node 2) was taken down for
maintenance.
The remaining two nodes seem to have issues gaining quorum.
I think the issues is that node 1 is taking 5 seconds to process notifications.
>From the logs, node 1 and node 3 both agree that node 3
Interestingly, the delay went away at the same time as node2 was brought back
up.
2018-09-14 09:33:30,944 - INFO
[QuorumPeer[myid=3]/0:0:0:0:0:0:0:0:2181:FastLeaderElection@813] - New
election. My id = 3, proposed zxid=0x61f52
2018-09-14 09:33:30,945 - INFO
Java 11 is out on Sept., 25 and makes Java 8, 9 and 10 obsolete. Java 8, 9,
and 10 will no longer receive security patches/updates beginning in January
2019. Organizations have the option to pay Oracle for patches in order to stay
on Java 8.
Oracle is changing its release cycle and
some port is not always be useding by a process, may be used at some time in
the past
so, from the zk log, i want to know which process accessed zk
wangyongqiang0...@163.com
From: Shawn Heisey
Date: 2018-09-12 18:10
To: user
Subject: Re: can not know the process name from zk log
On 9/12/2018
Hi,
What info exactly would you like to see about the client? What do you mean by
‘process info’?
Process name? That’s ‘java’ in 90% of cases and probably not enough to fully
identify the process.
Process ID?
This information currently not available in ZK, because the client doesn’t send
it
Hi Ram,
I might be missing something from your explanation, but that error message
alone is not an issue. All ZK nodes open connection to each other, but having 2
connections between the same nodes is redundant and one of them has to be
closed. To decide which one to close ZK use the server
