[jira] [Comment Edited] (STORM-3817) Upgrading to Zookeeper 3.5.x, 3.6.x or 3.7.x
[ https://issues.apache.org/jira/browse/STORM-3817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17490475#comment-17490475 ] Richard Zowalla edited comment on STORM-3817 at 2/10/22, 7:46 PM: -- Interesting. Looks odd to me, that the CI build approach is not affected. Maybe you can remove the exclusion in your PR, so we can be sure it builds in an IDE and in the CI (although you need the Travis fixes from the PR above). I migrated the exclusion from an older Zookeeper PR, so I do not insist on this "optimization" - so we can just drop it was (Author: rzo1): Interesting. Looks odd to me, that the CI build approach is not affected. Maybe you can remove the exclusion in your PR, so we can be sure it builds in an IDE and in the CI (although you need the Travis fixes from the PR above). I migrated the exclusion from an older Zookeeper PR, so I do not insist on this "optimization" > Upgrading to Zookeeper 3.5.x, 3.6.x or 3.7.x > > > Key: STORM-3817 > URL: https://issues.apache.org/jira/browse/STORM-3817 > Project: Apache Storm > Issue Type: Dependency upgrade >Affects Versions: 2.3.0, 2.2.1 >Reporter: Richard Zowalla >Priority: Major > Fix For: 2.4.0 > > Time Spent: 1h 50m > Remaining Estimate: 0h > > Is there any possibility to upgrade the [shaded zookeeper version > |https://github.com/apache/storm/blob/master/storm-shaded-deps/pom.xml#L64] > from 3.4.14 to a newer version? Or are there any reasons for not doing an > upgrade right now? > I am doing some testing with Storm in a Java 17 environment and it looks like > I am suffering from this Zookeeper specific issue present in 3.4.14: > https://issues.apache.org/jira/browse/ZOOKEEPER-3779 > If necessary I can also provide a PR for an upgrade to 3.5.x, 3.6.x or 3.7.x > UPDATE: Looks like curator depends on 3.5.x - so probably 3.5.x should be an > option. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Comment Edited] (STORM-3817) Upgrading to Zookeeper 3.5.x, 3.6.x or 3.7.x
[ https://issues.apache.org/jira/browse/STORM-3817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17490466#comment-17490466 ] Richard Zowalla edited comment on STORM-3817 at 2/10/22, 7:29 PM: -- [~ben.roling] interesting. There is a yetus exclusion in the storm deps shade in zookeeper jute. Does it work, If you remove the exclusion? However, it's weird that there is such a difference between CI / cmd Maven Builds. was (Author: rzo1): [~ben.roling] interesting. There is a yetus exclusion in the storm deps shade in zookeeper jute. Does is t work, If you remove the exclusion? However, it's weird that there is such a difference between CI / cmd Maven Builds. > Upgrading to Zookeeper 3.5.x, 3.6.x or 3.7.x > > > Key: STORM-3817 > URL: https://issues.apache.org/jira/browse/STORM-3817 > Project: Apache Storm > Issue Type: Dependency upgrade >Affects Versions: 2.3.0, 2.2.1 >Reporter: Richard Zowalla >Priority: Major > Fix For: 2.4.0 > > Time Spent: 1h 50m > Remaining Estimate: 0h > > Is there any possibility to upgrade the [shaded zookeeper version > |https://github.com/apache/storm/blob/master/storm-shaded-deps/pom.xml#L64] > from 3.4.14 to a newer version? Or are there any reasons for not doing an > upgrade right now? > I am doing some testing with Storm in a Java 17 environment and it looks like > I am suffering from this Zookeeper specific issue present in 3.4.14: > https://issues.apache.org/jira/browse/ZOOKEEPER-3779 > If necessary I can also provide a PR for an upgrade to 3.5.x, 3.6.x or 3.7.x > UPDATE: Looks like curator depends on 3.5.x - so probably 3.5.x should be an > option. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Comment Edited] (STORM-3817) Upgrading to Zookeeper 3.5.x, 3.6.x or 3.7.x
[ https://issues.apache.org/jira/browse/STORM-3817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17490466#comment-17490466 ] Richard Zowalla edited comment on STORM-3817 at 2/10/22, 7:28 PM: -- [~ben.roling] interesting. There is a yetus exclusion in the storm deps shade in zookeeper jute. Does is t work, If you remove the exclusion? However, it's weird that there is such a difference between CI / cmd Maven Builds. was (Author: rzo1): [~ben.roling] interesting. There is a yetus exclusion in the storm deps shade in zookeeper jute. Does ist work, If you remove the exclusion? However, it's weird that there is such a difference between CI / cmd Maven Builds. > Upgrading to Zookeeper 3.5.x, 3.6.x or 3.7.x > > > Key: STORM-3817 > URL: https://issues.apache.org/jira/browse/STORM-3817 > Project: Apache Storm > Issue Type: Dependency upgrade >Affects Versions: 2.3.0, 2.2.1 >Reporter: Richard Zowalla >Priority: Major > Fix For: 2.4.0 > > Time Spent: 1h 50m > Remaining Estimate: 0h > > Is there any possibility to upgrade the [shaded zookeeper version > |https://github.com/apache/storm/blob/master/storm-shaded-deps/pom.xml#L64] > from 3.4.14 to a newer version? Or are there any reasons for not doing an > upgrade right now? > I am doing some testing with Storm in a Java 17 environment and it looks like > I am suffering from this Zookeeper specific issue present in 3.4.14: > https://issues.apache.org/jira/browse/ZOOKEEPER-3779 > If necessary I can also provide a PR for an upgrade to 3.5.x, 3.6.x or 3.7.x > UPDATE: Looks like curator depends on 3.5.x - so probably 3.5.x should be an > option. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Comment Edited] (STORM-3817) Upgrading to Zookeeper 3.5.x, 3.6.x or 3.7.x
[ https://issues.apache.org/jira/browse/STORM-3817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17490466#comment-17490466 ] Richard Zowalla edited comment on STORM-3817 at 2/10/22, 7:28 PM: -- [~ben.roling] interesting. There is a yetus exclusion in the storm deps shade in zookeeper jute. Does ist work, If you remove the exclusion? However, it's weird that there is such a difference between CI / cmd Maven Builds. was (Author: rzo1): [~ben.roling] interesting. There is an yetus exclusion in the storm deps shade in zookeeper jute. Does ist work, If you remove the exclusion? However, it's weird that there is such a difference between CI / cmd Maven Builds. > Upgrading to Zookeeper 3.5.x, 3.6.x or 3.7.x > > > Key: STORM-3817 > URL: https://issues.apache.org/jira/browse/STORM-3817 > Project: Apache Storm > Issue Type: Dependency upgrade >Affects Versions: 2.3.0, 2.2.1 >Reporter: Richard Zowalla >Priority: Major > Fix For: 2.4.0 > > Time Spent: 1h 50m > Remaining Estimate: 0h > > Is there any possibility to upgrade the [shaded zookeeper version > |https://github.com/apache/storm/blob/master/storm-shaded-deps/pom.xml#L64] > from 3.4.14 to a newer version? Or are there any reasons for not doing an > upgrade right now? > I am doing some testing with Storm in a Java 17 environment and it looks like > I am suffering from this Zookeeper specific issue present in 3.4.14: > https://issues.apache.org/jira/browse/ZOOKEEPER-3779 > If necessary I can also provide a PR for an upgrade to 3.5.x, 3.6.x or 3.7.x > UPDATE: Looks like curator depends on 3.5.x - so probably 3.5.x should be an > option. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Comment Edited] (STORM-3817) Upgrading to Zookeeper 3.5.x, 3.6.x or 3.7.x
[ https://issues.apache.org/jira/browse/STORM-3817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17489928#comment-17489928 ] Richard Zowalla edited comment on STORM-3817 at 2/10/22, 2:54 AM: -- [~ben.roling] We have CI results available after putting the latest changes from master into the CI fix PR: https://github.com/apache/storm/pull/3437/checks?check_run_id=5132733294 which look good to me (no compile error). I built it the same way locally, so I am unsure, which causes the difference between me (+Travis) and the OSX setup. was (Author: rzo1): [~ben.roling] We have CI results after Putting the latest Changes from master into the CI fix PR: https://github.com/apache/storm/pull/3437/checks?check_run_id=5132733294 which look good to me (no compile error). I built it the same way locally, so I am unsure, which causes the difference between me (+Travis) and the OSX setup. > Upgrading to Zookeeper 3.5.x, 3.6.x or 3.7.x > > > Key: STORM-3817 > URL: https://issues.apache.org/jira/browse/STORM-3817 > Project: Apache Storm > Issue Type: Dependency upgrade >Affects Versions: 2.3.0, 2.2.1 >Reporter: Richard Zowalla >Priority: Major > Fix For: 2.4.0 > > Time Spent: 1h 50m > Remaining Estimate: 0h > > Is there any possibility to upgrade the [shaded zookeeper version > |https://github.com/apache/storm/blob/master/storm-shaded-deps/pom.xml#L64] > from 3.4.14 to a newer version? Or are there any reasons for not doing an > upgrade right now? > I am doing some testing with Storm in a Java 17 environment and it looks like > I am suffering from this Zookeeper specific issue present in 3.4.14: > https://issues.apache.org/jira/browse/ZOOKEEPER-3779 > If necessary I can also provide a PR for an upgrade to 3.5.x, 3.6.x or 3.7.x > UPDATE: Looks like curator depends on 3.5.x - so probably 3.5.x should be an > option. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Comment Edited] (STORM-3817) Upgrading to Zookeeper 3.5.x, 3.6.x or 3.7.x
[ https://issues.apache.org/jira/browse/STORM-3817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17489842#comment-17489842 ] Richard Zowalla edited comment on STORM-3817 at 2/9/22, 10:35 PM: -- Interesting. Local build via the Travis script in a Ubuntu 16.04 VM worked fine for me creating the (merged) PR. I just fetched the latest changes from master and put them into the PR regarding the Travis CI with the change, so we get some CI Feedback soon. was (Author: rzo1): Interesting. Local build via the Travis script in a Ubuntu 16.04 VM worked fine for me creating the (merged) PR. I just fetched the latest changes from master and Put them into the PR regarding the Travis CI with the change, so we get some CI Feedback soon. > Upgrading to Zookeeper 3.5.x, 3.6.x or 3.7.x > > > Key: STORM-3817 > URL: https://issues.apache.org/jira/browse/STORM-3817 > Project: Apache Storm > Issue Type: Dependency upgrade >Affects Versions: 2.3.0, 2.2.1 >Reporter: Richard Zowalla >Priority: Major > Fix For: 2.4.0 > > Time Spent: 1h 50m > Remaining Estimate: 0h > > Is there any possibility to upgrade the [shaded zookeeper version > |https://github.com/apache/storm/blob/master/storm-shaded-deps/pom.xml#L64] > from 3.4.14 to a newer version? Or are there any reasons for not doing an > upgrade right now? > I am doing some testing with Storm in a Java 17 environment and it looks like > I am suffering from this Zookeeper specific issue present in 3.4.14: > https://issues.apache.org/jira/browse/ZOOKEEPER-3779 > If necessary I can also provide a PR for an upgrade to 3.5.x, 3.6.x or 3.7.x > UPDATE: Looks like curator depends on 3.5.x - so probably 3.5.x should be an > option. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Comment Edited] (STORM-3817) Upgrading to Zookeeper 3.5.x, 3.6.x or 3.7.x
[ https://issues.apache.org/jira/browse/STORM-3817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17489842#comment-17489842 ] Richard Zowalla edited comment on STORM-3817 at 2/9/22, 10:34 PM: -- Interesting. Local build via the Travis script in a Ubuntu 16.04 VM worked fine for me creating the (merged) PR. I just fetched the latest changes from master and Put them into the PR regarding the Travis CI with the change, so we get some CI Feedback soon. was (Author: rzo1): Interesting. Local build via the Travis script in a Ubuntu 16.04 VM worked fine for me. I just fetched the latest changes from master and Put them into the PR regarding the Travis CI with the change, so we get some CI Feedback soon. > Upgrading to Zookeeper 3.5.x, 3.6.x or 3.7.x > > > Key: STORM-3817 > URL: https://issues.apache.org/jira/browse/STORM-3817 > Project: Apache Storm > Issue Type: Dependency upgrade >Affects Versions: 2.3.0, 2.2.1 >Reporter: Richard Zowalla >Priority: Major > Fix For: 2.4.0 > > Time Spent: 1h 50m > Remaining Estimate: 0h > > Is there any possibility to upgrade the [shaded zookeeper version > |https://github.com/apache/storm/blob/master/storm-shaded-deps/pom.xml#L64] > from 3.4.14 to a newer version? Or are there any reasons for not doing an > upgrade right now? > I am doing some testing with Storm in a Java 17 environment and it looks like > I am suffering from this Zookeeper specific issue present in 3.4.14: > https://issues.apache.org/jira/browse/ZOOKEEPER-3779 > If necessary I can also provide a PR for an upgrade to 3.5.x, 3.6.x or 3.7.x > UPDATE: Looks like curator depends on 3.5.x - so probably 3.5.x should be an > option. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Comment Edited] (STORM-3817) Upgrading to Zookeeper 3.5.x, 3.6.x or 3.7.x
[ https://issues.apache.org/jira/browse/STORM-3817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17489842#comment-17489842 ] Richard Zowalla edited comment on STORM-3817 at 2/9/22, 10:33 PM: -- Interesting. Local build via the Travis script in a Ubuntu 16.04 VM worked fine for me. I just fetched the latest changes from master and Put them into the PR regarding the Travis CI with the change, so we get some CI Feedback soon. was (Author: rzo1): Interesting. Local build via the Travis script works for me in Ubuntu with it. I just updated the PR regarding the Travis CI with the change, so we get some CI Feedback soon. > Upgrading to Zookeeper 3.5.x, 3.6.x or 3.7.x > > > Key: STORM-3817 > URL: https://issues.apache.org/jira/browse/STORM-3817 > Project: Apache Storm > Issue Type: Dependency upgrade >Affects Versions: 2.3.0, 2.2.1 >Reporter: Richard Zowalla >Priority: Major > Fix For: 2.4.0 > > Time Spent: 1h 50m > Remaining Estimate: 0h > > Is there any possibility to upgrade the [shaded zookeeper version > |https://github.com/apache/storm/blob/master/storm-shaded-deps/pom.xml#L64] > from 3.4.14 to a newer version? Or are there any reasons for not doing an > upgrade right now? > I am doing some testing with Storm in a Java 17 environment and it looks like > I am suffering from this Zookeeper specific issue present in 3.4.14: > https://issues.apache.org/jira/browse/ZOOKEEPER-3779 > If necessary I can also provide a PR for an upgrade to 3.5.x, 3.6.x or 3.7.x > UPDATE: Looks like curator depends on 3.5.x - so probably 3.5.x should be an > option. -- This message was sent by Atlassian Jira (v8.20.1#820001)
