[ https://issues.apache.org/jira/browse/CURATOR-519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Raúl Gracia Tinedo updated CURATOR-519: --------------------------------------- Description: We are using Curator 4.0.1 in our project (Pravega, [https://github.com/pravega/pravega]). Just for context, we are intensively deploying Pravega on Kubernetes. In this sense, Zookeeper (3.5.4-beta) is also being deployed as a service in Kubernetes. In this environment, Zookeeper instances (i.e., pods) can be frequently restarted or relocated and their IP may change. Properly handling this situation requires to re-resolve the IP for hostname of Zookeeper instances. In fact, we are experiencing problems with this exact issue with Curator 4.0.1 (i.e., re-resolution of Zookeeper hostnames), which internally uses Zookeeper 3.5.3-beta as a dependency. Details can be found in this GitHub issue: [https://github.com/pravega/pravega/issues/3651] Fortunately, the proper resolution of Zookeepr hostnames has been actually reported and fixed in the Zookeeper project: - Issue: https://issues.apache.org/jira/browse/ZOOKEEPER-2184 - Commit on Zookeeper 3.5.5 branch: [https://github.com/apache/zookeeper/commit/1e65b9f4873fc995308972433ea8a664e98fe41f] To verify that it helps us to solve our problem, I have built a custom Curator 4.0.1 library using Zookeeper 3.5.5 and then I used that library to build a Pravega image. A couple of comments to take into account: - Using Zookeeper 3.5.5 to build Curator 4.0.1 required no code change, just changing the Zookeeper dependency version in the pom.xml (I had the same experience with Curator 4.1.0). - I verified that using Curator 4.0.1 and 4.1.0 with Zookeeper 3.5.5 solves the re-resolution of Zookeeper hostnames, which makes our system able to properly handle Zookeeper instance restarts. Therefore, the main point of this issue is: _is in the roadmap to release Curator 4.0.x and/or 4.1.x using Zookeeper 3.5.5?_ (Note that Zookeeper 3.5.5 is about to get released: [https://github.com/apache/zookeeper/releases]) Thanks in advance, Raúl. was: We are using Curator 4.0.1 in our project (Pravega, [https://github.com/pravega/pravega]). Just for context, we are intensively deploying Pravega on Kubernetes. In this sense, Zookeeper (3.5.4-beta) is also being deployed as a service in Kubernetes. In this environment, Zookeeper instances (i.e., pods) can be frequently restarted or relocated and their IP may change. Properly handling this situation requires to re-resolve the IP for hostname of Zookeeper instances. In fact, we are experiencing problems with this exact issue with Curator 4.0.1 (i.e., re-resolution of Zookeeper hostnames), which internally uses Zookeeper 3.5.3-beta as a dependency. Details can be found in this GitHub issue: [https://github.com/pravega/pravega/issues/3651 ] Fortunately, the proper resolution of Zookeepr hostnames has been actually reported and fixed in the Zookeeper project: - Issue: https://issues.apache.org/jira/browse/ZOOKEEPER-2184 - Commit on Zookeeper 3.5.5 branch: [https://github.com/apache/zookeeper/commit/1e65b9f4873fc995308972433ea8a664e98fe41f] To verify that it helps us to solve our problem, I have built a custom Curator 4.0.1 library using Zookeeper 3.5.5 and then I used that library to build a Pravega image. A couple of comments to take into account: - Using Zookeeper 3.5.5 to build Curator 4.0.1 required no code change, just changing the Zookeeper dependency version in the pom.xml (I had the same experience with Curator 4.1.0). - I verified that using Curator 4.0.1 and 4.1.0 with Zookeeper 3.5.5 solves the re-resolution of Zookeeper hostnames, which makes our system able to properly handle Zookeeper instance restarts. Therefore, the main point of this issue is: _is in the roadmap to release Curator 4.0.x and/or 4.1.x using Zookeeper 3.5.5?_ (Note that Zookeeper 3.5.5 is about to get released: [https://github.com/apache/zookeeper/releases]) Thanks in advance, Raúl. > Curator 4.0.x/4.1.x release using Zookeeper 3.5.5 > -------------------------------------------------- > > Key: CURATOR-519 > URL: https://issues.apache.org/jira/browse/CURATOR-519 > Project: Apache Curator > Issue Type: Wish > Components: General > Affects Versions: 4.0.1, 4.1.0 > Reporter: Raúl Gracia Tinedo > Priority: Major > Labels: easyfix > > We are using Curator 4.0.1 in our project (Pravega, > [https://github.com/pravega/pravega]). > Just for context, we are intensively deploying Pravega on Kubernetes. In this > sense, Zookeeper (3.5.4-beta) is also being deployed as a service in > Kubernetes. In this environment, Zookeeper instances (i.e., pods) can be > frequently restarted or relocated and their IP may change. Properly handling > this situation requires to re-resolve the IP for hostname of Zookeeper > instances. > In fact, we are experiencing problems with this exact issue with Curator > 4.0.1 (i.e., re-resolution of Zookeeper hostnames), which internally uses > Zookeeper 3.5.3-beta as a dependency. Details can be found in this GitHub > issue: [https://github.com/pravega/pravega/issues/3651] > > Fortunately, the proper resolution of Zookeepr hostnames has been actually > reported and fixed in the Zookeeper project: > - Issue: https://issues.apache.org/jira/browse/ZOOKEEPER-2184 > - Commit on Zookeeper 3.5.5 branch: > [https://github.com/apache/zookeeper/commit/1e65b9f4873fc995308972433ea8a664e98fe41f] > > To verify that it helps us to solve our problem, I have built a custom > Curator 4.0.1 library using Zookeeper 3.5.5 and then I used that library to > build a Pravega image. A couple of comments to take into account: > - Using Zookeeper 3.5.5 to build Curator 4.0.1 required no code change, just > changing the Zookeeper dependency version in the pom.xml (I had the same > experience with Curator 4.1.0). > - I verified that using Curator 4.0.1 and 4.1.0 with Zookeeper 3.5.5 solves > the re-resolution of Zookeeper hostnames, which makes our system able to > properly handle Zookeeper instance restarts. > > Therefore, the main point of this issue is: _is in the roadmap to release > Curator 4.0.x and/or 4.1.x using Zookeeper 3.5.5?_ (Note that Zookeeper 3.5.5 > is about to get released: [https://github.com/apache/zookeeper/releases]) > > Thanks in advance, > Raúl. -- This message was sent by Atlassian JIRA (v7.6.3#76005)