AW: ZooKeeper 3.4.9: ACL based on IPv6 addresses
Hi Patrick, I was testing with ACLs on several Linux machines trying to allow access from localhost and a remote address. The machines use both IPv4 and IPv6 on different network interfaces. Localhost is being translated to IPv6 ::1. I was trying to set an ACL allowing access from localhost and a remote machine. The remote machine uses IPv4 in this case, but localhost is IPv6, so that the ACL declared for 127.0.0.1 is not recognized. My workaround is currently enforcing the JVMs to use IPv4 in any case by setting the command line argument -Djava.net.preferIPv4Stack=true on all zookeeper server and client instances. ciao Thomas -Ursprüngliche Nachricht- Von: Patrick Hunt [mailto:ph...@apache.org] Gesendet: Mittwoch, 4. Oktober 2017 19:52 An: UserZooKeeper Betreff: Re: ZooKeeper 3.4.9: ACL based on IPv6 addresses Hi Thomas, I don't have any experience with this but I'm interested to know if you figured this out? If so would you be able to submit a jira and patch with a doc change explaining it? Or at the very least submit a jira explaining so that someone else can replicate/document? Thanks! Patrick On Wed, Sep 27, 2017 at 2:57 AM, Thomas Ta Keßler < thomas.ta.kess...@deutschebahn.com> wrote: > Hello, > > I would like to configure some ACL based on IPv6 addresses. > Unfortunately I do not find any documentation on this topic. The only > documentation refers to IPv4 addresses, a command would look like this using > CLI: > setAcl / ip:127.0.0.1:crdwa,ip:10.179.82.34:crdwa > > Does anyone know how to do it? Or maybe as a workaround how to > configure hostname based ACLs? > > Thank you... > Thomas >
Zookeeper quorum goes down for no apparent reason in 3.4.5
Hi, We have an issue with a 3-node zookeeper ensemble where the quorum goes down due to no apparent reason every once in a while. Here is what I see in the ZK leader: 2017-09-21 03:00:03,648 [myid:3] - INFO [QuorumPeer[myid=3]/127.0.0.1:5002 :Leader@493] - Shutting down 2017-09-21 03:00:03,648 [myid:3] - INFO [QuorumPeer[myid=3]/127.0.0.1:5002 :Leader@499] - Shutdown called java.lang.Exception: shutdown Leader! reason: Not sufficient followers synced, only synced with sids: [ 3 ] at org.apache.zookeeper.server.quorum.Leader.shutdown(Leader.java:499) at org.apache.zookeeper.server.quorum.Leader.lead(Leader.java:474) at org.apache.zookeeper.server.quorum.QuorumPeer.run(QuorumPeer.java:799) I have attached the logs from the 3 nodes around this time. Could you pls. help understand what the issue could be here. The only thing I see a little bit ahead of this timestamp is that all of them did a PurgeTask pretty much at the same time. Thanks, Anand.
Re: ZooKeeper 3.4.9: ACL based on IPv6 addresses
Hi Thomas, I don't have any experience with this but I'm interested to know if you figured this out? If so would you be able to submit a jira and patch with a doc change explaining it? Or at the very least submit a jira explaining so that someone else can replicate/document? Thanks! Patrick On Wed, Sep 27, 2017 at 2:57 AM, Thomas Ta Keßler < thomas.ta.kess...@deutschebahn.com> wrote: > Hello, > > I would like to configure some ACL based on IPv6 addresses. Unfortunately > I do not find any documentation on this topic. The only documentation > refers to IPv4 addresses, a command would look like this using CLI: > setAcl / ip:127.0.0.1:crdwa,ip:10.179.82.34:crdwa > > Does anyone know how to do it? Or maybe as a workaround how to configure > hostname based ACLs? > > Thank you... > Thomas >
Re: When zookeeper 3.5 version can go to final stable ?
Hi, last update on this was a few days ago, please see the archives. https://lists.apache.org/thread.html/2d006f5914d5b06777efe378422820 8f889e66f903b561251758e08c@%3Cdev.zookeeper.apache.org%3E Regards, Patrick On Mon, Oct 2, 2017 at 5:03 AM, L. J.W wrote: > When zookeeper 3.5 version can go to final stable ? We expect for the local > session feature and wait for stable version to use in our product > environment. > any plan? > > L.J.W >
