'zkServer.sh status' connects only to local node ?

2019-12-12 Thread prashantkumar dhotre
Hi, Could you please help me with a basic query regarding 'zkServer.sh status' ? >From zkServer.sh, it appears that this cmd tries to connect to server at local node and get info. If the local server is down, does it connect to next available server (as specified in config file ) and returns

Re: default value for quorum.auth.kerberos.servicePrincipal

2019-12-12 Thread Rakesh Radhakrishnan
Hi Ram, ZooKeeper Quorum authentication support two schemes, Kerberos or DIGEST-MD5. User has to configure either Kerb or digest configuration values. Both together not required. I'd recommend you to go through Kerberos, digest simulation unit test cases where we have valid and invalid

Re: Snapshot creation after 3.4.14 -> 3.5.6 upgrade

2019-12-12 Thread Michael Han
>> My question is: Is there a way to force the snapshot creation / sync from the leader? 3.5.6 will automatically create a clean snapshot as part of server start up process. So a snapshot should be available after initial upgrade and there is no need to force a snapshot creation. On Mon, Dec 9,

Re: clientCnxnSocket#updateLastSendAndHeard() method usage

2019-12-12 Thread Michael Han
We had some prod issues previously related to the usage of cached "now" variable (and lacking of consistent accessing pattern for updateNow) used in java client - we had a patch internally (basically what's described in ZOOKEEPER-2471) that removed usage of the cache value and instead calculate

Re: Zookeeper SSL C Client Support

2019-12-12 Thread Szalay-Bekő Máté
Hi Pradeep, based on the logs, it seems working. It is great to see that you will use it :) Let us know if you would see any issue with it. FYI, we already have a few improvements under review around these areas: - https://issues.apache.org/jira/browse/ZOOKEEPER-3567 (Add SSL support for the zk

Disable non-secured client port

2019-12-12 Thread Chris T.
Hi, we're working on securing our clusters. For quorum, once we set sslQuorum=true, there is no more unsecured quorum port. Is such an option available or in the works for the client port as well ? Or is ssl client port always in addition to unsecured client port ? Regards, Chris

Re: ZK makes apache 2019 "top 5" projects

2019-12-12 Thread Jordan Zimmerman
Fantastic Jordan Zimmerman > On Dec 12, 2019, at 3:49 AM, Flavio Junqueira wrote: > > +1, thank you all for the hard work. > > -Flavio > >> On 12 Dec 2019, at 08:36, Enrico Olivelli wrote: >> >> Yes, great. >> >> Please also note that Kafka and Lucene/Solr that are

Re: quorum.cnxn.threads.size

2019-12-12 Thread rammohan ganapavarapu
Any idea? On Wed, Dec 11, 2019, 2:23 PM rammohan ganapavarapu wrote: > And to add more on the same property, the description says > > > > > > *"For example, consider a 3-node cluster,# during quorum formation at > least 3 outgoing connection requests and 3 incoming connection# requests > will

Re: ZK makes apache 2019 "top 5" projects

2019-12-12 Thread Flavio Junqueira
+1, thank you all for the hard work. -Flavio > On 12 Dec 2019, at 08:36, Enrico Olivelli wrote: > > Yes, great. > > Please also note that Kafka and Lucene/Solr that are still listed in that > list are using Zookeeper :) > > > Enrico > > Il gio 12 dic 2019, 05:46 tison ha scritto: > >>

Re: Disable non-secured client port

2019-12-12 Thread Chris T.
Great, thanks. On Thu, Dec 12, 2019 at 3:53 PM Szalay-Bekő Máté wrote: > Hi Chris, > > The short answer is yes, all you need to do is don't specify the clientPort > in the zoo.cfg. > > An example for the zoo.cfg in this case: > > tickTime=3000 > initLimit=10 > syncLimit=5 > dataDir=/data/zkdata

Re: quorum.cnxn.threads.size

2019-12-12 Thread rammohan ganapavarapu
Flavio, Thanks for clarification, I have a cluster with sasl disabled but in start up log I still see number of threads set to default 20. Thanks, Ram On Thu, Dec 12, 2019, 6:43 AM Flavio Junqueira wrote: > Hi Ram, > > Yes, this parameter is only applicable when SASL is enabled, see in >

Re: quorum.cnxn.threads.size

2019-12-12 Thread Flavio Junqueira
If it is just logging the value of the property, then it is fine because the property is set, but it is not used if SASL is disabled. -Flavio > On 12 Dec 2019, at 16:01, rammohan ganapavarapu > wrote: > > Flavio, > > Thanks for clarification, I have a cluster with sasl disabled but in start

Re: quorum.cnxn.threads.size

2019-12-12 Thread Flavio Junqueira
Hi Ram, Yes, this parameter is only applicable when SASL is enabled, see in QuorumCnxManager#initializeAuth how it doesn't have a chance to use the parameter when SASL is disabled. Your assessment is correct about it being based on the number of participants, excluding observers. This

Re: Disable non-secured client port

2019-12-12 Thread Szalay-Bekő Máté
Hi Chris, The short answer is yes, all you need to do is don't specify the clientPort in the zoo.cfg. An example for the zoo.cfg in this case: tickTime=3000 initLimit=10 syncLimit=5 dataDir=/data/zkdata secureClientPort=2191 serverCnxnFactory=org.apache.zookeeper.server.NettyServerCnxnFactory

Re: ZK makes apache 2019 "top 5" projects

2019-12-12 Thread Norbert Kalmar
Kudos to everyone! Also, nice to see so many contributions. And not just veterans, but plenty of new community members! Thank you all! Regards, Norbert On Thu, Dec 12, 2019 at 2:00 PM Jordan Zimmerman wrote: > Fantastic > > > Jordan Zimmerman > > > On Dec 12, 2019, at 3:49

Re: quorum.cnxn.threads.size

2019-12-12 Thread rammohan ganapavarapu
I am assuming its only logging, is there any way i can verify its not opening cnxn threads? On Thu, Dec 12, 2019 at 7:15 AM Flavio Junqueira wrote: > If it is just logging the value of the property, then it is fine because > the property is set, but it is not used if SASL is disabled. > >

Re: Notification messages in log

2019-12-12 Thread rammohan ganapavarapu
Any thoughts? On Wed, Dec 11, 2019 at 7:48 PM rammohan ganapavarapu < rammohanga...@gmail.com> wrote: > Hi Enrico, > > Since i have log rotation, i am not worried about size but i see ~14 such > messages for a second which seems unusual for me. > > grep "Notification: 0 (message format

Re: quorum.cnxn.threads.size

2019-12-12 Thread Flavio Junqueira
If you set up logging at DEBUG level and you see this message: "Not initializing connection executor as quorum sasl auth is disabled" then you are good. -Flavio > On 12 Dec 2019, at 18:06, rammohan ganapavarapu > wrote: > > I am assuming its only logging, is there any way i can verify its

Re: quorum.cnxn.threads.size

2019-12-12 Thread rammohan ganapavarapu
No, my loglevel setting is INFO. ps -ef |grep zoo|awk '{print $10}' -Dzookeeper.root.logger=INFO,CONSOLE Just to clarify, i am upgrading from 3.4.5 to 3.4.14 and i am upgrading observers firs then followers (yet to do) and see this flood of log messages in observer logs. Observer: 3.4.14

Re: default value for quorum.auth.kerberos.servicePrincipal

2019-12-12 Thread rammohan ganapavarapu
Hi, Even if i enable sasl but md5-diget what should be this property set to, this property only take effect for kerberos or for both? Ram On Fri, Dec 6, 2019 at 7:55 AM rammohan ganapavarapu < rammohanga...@gmail.com> wrote: > Mate, > > Thank you, I did search source code found the same, I am