Re: Upgrade required Java version to 1.8 on 3.5+

2018-03-08 Thread Andor Molnar
Hi Shawn, Thanks for the feedback and thanks for everybody else too. The short term plan is to introduce Java 8 in next upcoming stable release, 3.5. Jumping 2 Java versions seems to be too much for me too. ZK master branch is going to be 3.6 release in which we can talk about upgrading to Java

Re: Zookeeper general log or “monitor” command

2018-03-08 Thread Nikhil Bafna
> If I understand correctly, a slow operation log with the threshold for > logging set to 0 should accomplish what you are trying to accomplish. Yes, that would work. You may also want to consider taking a look and reviewing the change > proposed here:

core in netlink with "Unexpected error 9 on netlink descriptor 20" error

2018-03-08 Thread prashantkumar dhotre
Hi Could you please let me know if this issue is already resolved or if we have an exisiting bug already for below issue issue:core in netlink with "Unexpected error 9 on netlink descriptor 20" error https://issues.apache.org/jira/browse/ZOOKEEPER-2996 Thanks

RE: SASL for Client connections

2018-03-08 Thread Ray Chaudhuri, Shirsha (Nokia - IN/Bangalore)
Hi Abe, We are trying to understand the difference between setting requireClientAuthScheme=sasl and requireClientAuthScheme=all When a client does not have a valid Kerberos ticket, the behaviour is the same for either of the above settings. Whereas we'd've expected the client to not be able to

Re: Upgrade required Java version to 1.8 on 3.5+

2018-03-08 Thread Shawn Heisey
On 3/7/2018 1:21 PM, Jeff Widman wrote: > +1 from me to using Java 8 or even going all the way to 9 for the 3.5 > release branch. I don't think it would be a good idea to require Java 9 at this time.  It's probably already an uphill battle for sysadmins to get approval to jump ONE major version. 

Re: Zookeeper general log or “monitor” command

2018-03-08 Thread Abraham Fine
You may also want to consider taking a look and reviewing the change proposed here: https://github.com/apache/zookeeper/pull/307 If I understand correctly, a slow operation log with the threshold for logging set to 0 should accomplish what you are trying to accomplish. Thanks, Abe On Wed, Mar

Re: SASL for Client connections

2018-03-08 Thread Abraham Fine
Hi Harish- Currently there is no way to restrict ALL incoming client connections when using SASL. In ZooKeeper, SASL works on a node by node basis. Thanks, Abe On Thu, Mar 8, 2018, at 03:58, Harish kumar wrote: > Hi, > > I have enabled SASL on my Zookeeper, with below configuration. > >

SASL for Client connections

2018-03-08 Thread Harish kumar
Hi, I have enabled SASL on my Zookeeper, with below configuration. *requireClientAuthScheme=sasl* *authProvider.1=org.apache.zookeeper.server.auth.SASLAuthenticationProvider* But still I see that, I am able to connect to zookeeper even without a valid kerberos ticket. Is there a way to restrict