Re: [VOTE] Apache ZooKeeper release 3.6.4 candidate 0
> I have confirmed that I can build the current branch-3.6 on my machine, using GCC 12.2.0. Thank you for testing it!! > Does the build/test pipeline need to be updated to verify this? Why make it a manual/release step. > Perhaps part of the reason we're seeing this now is lack of CI on branch-3.6. Yes, the CI is simpler on branch-3.6. We have some CI, a PR jenkins job is is building java and C code and runs all the tests ( https://ci-hadoop.apache.org/blue/organizations/jenkins/zookeeper-precommit-github-pr/detail/PR-1965/1/pipeline) but we definitely miss the new github CI checks on this old branch. On the other hand, even on newer branches we don't have any explicit checks to build and test the C code with a matrix of GCC versions and libraries. We could do something similar to how we test the Java code with multiple JDK versions. (or at least add a few docker files that one can use locally to have test environments with more important gcc/library version combinations) Anyway, I knew about this problem based on other failures on newer branches. I guess I should have waited for the fix to be merged before cutting the release. I am cancelling this VOTE for 3.6.4 RC 0 now. I will send RC 1 soon. Thank you for your time and feedback! Máté On Fri, Dec 16, 2022 at 1:45 AM Chris Nauroth wrote: > I have confirmed that I can build the current branch-3.6 on my machine, > using GCC 12.2.0. I agree with your point that the GCC version might not be > root cause, and it's also possible that it's caused by a difference in > OpenSSL headers. My OpenSSL version is 3.0.7. > > Perhaps part of the reason we're seeing this now is lack of CI on > branch-3.6. If we had CI on that branch, then we would have seen failures > in recent branch-3.6 pull requests, like this one: > > https://github.com/apache/zookeeper/pull/1965 > > Chris Nauroth > > > On Thu, Dec 15, 2022 at 3:39 PM Patrick Hunt wrote: > > > Does the build/test pipeline need to be updated to verify this? Why make > it > > a manual/release step. > > > > Patrick > > > > On Thu, Dec 15, 2022 at 3:35 PM Szalay-Bekő Máté < > > szalay.beko.m...@gmail.com> > > wrote: > > > > > Thanks for checking! > > > > > > I don't have a strong opinion. It would make sense to support newer gcc > > > versions in a new release. On the other hand, it is not a regression on > > the > > > branch-3.6 (the c-client in this rc compiles with the same gcc versions > > > which were compatible with 3.6 3). > > > > > > But I am OK to make a new RC. I don't have new gcc installed though to > > test > > > it locally. Also, I wonder if installing a new gcc is enough, or the > > > openssl or other library versions also matter? > > > > > > Could you maybe check if the current branch-3.6 compiles on your > machine, > > > with gcc 12.2.0? As you mentioned, the fix for ZOOKEEPER-4641 is > already > > > present there (I merged it after RC 0). If it works for you, then I can > > add > > > this commit and cut RC 1. > > > > > > Unless someone disagree... > > > > > > Thanks, > > > Máté > > > > > > > > > On Thu, Dec 15, 2022, 6:45 PM Chris Nauroth > wrote: > > > > > > > Unfortunately, I can't compile the C client because of the FIPS_mode > > bug > > > > (ZOOKEEPER-4641). I'm on a newer version of GCC: 12.2.0. I see that > > > > ZOOKEEPER-4641 was committed to branch-3.6 with a fix version of > 3.6.5. > > > > However, we're intending that 3.6.4 is the final 3.6 release, so > there > > > > never will be a 3.6.5. > > > > > > > > Sorry for the churn, but I'd prefer if we could bring that fix into a > > new > > > > release candidate. Let me know your thoughts on it. > > > > > > > > Chris Nauroth > > > > > > > > > > > > On Wed, Dec 14, 2022 at 4:08 PM Szalay-Bekő Máté < > > > > szalay.beko.m...@gmail.com> > > > > wrote: > > > > > > > > > +1 (binding) > > > > > > > > > > I did the following tests for the release candidate: > > > > > - verified checksum and gpg signature of the artifacts > > > > > - I built the source code (incl. the C-client, using -Pfull-build) > on > > > > > Ubuntu 20.04.5 using OpenJDK 8u352, maven 3.6.3 and GCC version > 9.4.0 > > > > > - all the unit tests passed (both Java and C-client) > > > > > - I also built and executed unit tests for zkpython > > > > > - I also built the java code (without -Pfull-build) using other JDK > > > > > versions: 11.0.15, 17.0.3, 18.0.1, 19.0.1 (but didn't run the tests > > > this > > > > > time, just used 'clean install -DskipTests') > > > > > - checkstyle and spotbugs passed > > > > > - apache-rat passed > > > > > - owasp (CVE check) passed > > > > > - fatjar built > > > > > - I executed quick rolling-upgrade tests (using > > > > > https://github.com/symat/zk-rolling-upgrade-test): > > > > > - rolling upgrade from 3.5.10 to 3.6.4 > > > > > - rolling upgrade from 3.6.3 to 3.6.4 > > > > > - rolling upgrade from 3.6.4 to 3.7.1 > > > > > - rolling upgrade from 3.6.4 to 3.8.0 > > > > > - checked the generated documentation
Re: [VOTE] Apache ZooKeeper release 3.6.4 candidate 0
I have confirmed that I can build the current branch-3.6 on my machine, using GCC 12.2.0. I agree with your point that the GCC version might not be root cause, and it's also possible that it's caused by a difference in OpenSSL headers. My OpenSSL version is 3.0.7. Perhaps part of the reason we're seeing this now is lack of CI on branch-3.6. If we had CI on that branch, then we would have seen failures in recent branch-3.6 pull requests, like this one: https://github.com/apache/zookeeper/pull/1965 Chris Nauroth On Thu, Dec 15, 2022 at 3:39 PM Patrick Hunt wrote: > Does the build/test pipeline need to be updated to verify this? Why make it > a manual/release step. > > Patrick > > On Thu, Dec 15, 2022 at 3:35 PM Szalay-Bekő Máté < > szalay.beko.m...@gmail.com> > wrote: > > > Thanks for checking! > > > > I don't have a strong opinion. It would make sense to support newer gcc > > versions in a new release. On the other hand, it is not a regression on > the > > branch-3.6 (the c-client in this rc compiles with the same gcc versions > > which were compatible with 3.6 3). > > > > But I am OK to make a new RC. I don't have new gcc installed though to > test > > it locally. Also, I wonder if installing a new gcc is enough, or the > > openssl or other library versions also matter? > > > > Could you maybe check if the current branch-3.6 compiles on your machine, > > with gcc 12.2.0? As you mentioned, the fix for ZOOKEEPER-4641 is already > > present there (I merged it after RC 0). If it works for you, then I can > add > > this commit and cut RC 1. > > > > Unless someone disagree... > > > > Thanks, > > Máté > > > > > > On Thu, Dec 15, 2022, 6:45 PM Chris Nauroth wrote: > > > > > Unfortunately, I can't compile the C client because of the FIPS_mode > bug > > > (ZOOKEEPER-4641). I'm on a newer version of GCC: 12.2.0. I see that > > > ZOOKEEPER-4641 was committed to branch-3.6 with a fix version of 3.6.5. > > > However, we're intending that 3.6.4 is the final 3.6 release, so there > > > never will be a 3.6.5. > > > > > > Sorry for the churn, but I'd prefer if we could bring that fix into a > new > > > release candidate. Let me know your thoughts on it. > > > > > > Chris Nauroth > > > > > > > > > On Wed, Dec 14, 2022 at 4:08 PM Szalay-Bekő Máté < > > > szalay.beko.m...@gmail.com> > > > wrote: > > > > > > > +1 (binding) > > > > > > > > I did the following tests for the release candidate: > > > > - verified checksum and gpg signature of the artifacts > > > > - I built the source code (incl. the C-client, using -Pfull-build) on > > > > Ubuntu 20.04.5 using OpenJDK 8u352, maven 3.6.3 and GCC version 9.4.0 > > > > - all the unit tests passed (both Java and C-client) > > > > - I also built and executed unit tests for zkpython > > > > - I also built the java code (without -Pfull-build) using other JDK > > > > versions: 11.0.15, 17.0.3, 18.0.1, 19.0.1 (but didn't run the tests > > this > > > > time, just used 'clean install -DskipTests') > > > > - checkstyle and spotbugs passed > > > > - apache-rat passed > > > > - owasp (CVE check) passed > > > > - fatjar built > > > > - I executed quick rolling-upgrade tests (using > > > > https://github.com/symat/zk-rolling-upgrade-test): > > > > - rolling upgrade from 3.5.10 to 3.6.4 > > > > - rolling upgrade from 3.6.3 to 3.6.4 > > > > - rolling upgrade from 3.6.4 to 3.7.1 > > > > - rolling upgrade from 3.6.4 to 3.8.0 > > > > - checked the generated documentation (zookeeper-docs/target/html) > > > > - compared generated release notes (releasenotes.html) with Jira ( > > > > > > > > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310801=12350076 > > > > ) > > > > > > > > Best regards, > > > > Máté > > > > > > > > On Thu, Dec 15, 2022 at 1:05 AM Szalay-Bekő Máté < > > > > szalay.beko.m...@gmail.com> > > > > wrote: > > > > > > > > > This is a bugfix release candidate for 3.6.4. It fixes 40 issues, > > > > > including CVE fixes, > > > > > log4j1 removal (using reload4j from now) and various other bug > fixes > > > > > (thread leaks, data > > > > > corruption, snapshotting and SASL related fixes). > > > > > > > > > > Please note, that based on our Release Strategy ( > > > > > https://zookeeper.apache.org/releases.html#release-strategy) > branch > > > 3.6 > > > > > should become end-of-life and most likely 3.6.4 will be our last > 3.6 > > > > > release. > > > > > > > > > > The full release notes is available at: > > > > > > > > > > > > > > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310801=12350076 > > > > > > > > > > *** Please download, test and vote by December 23th 2022, 23:59 > > UTC+0. > > > > *** > > > > > > > > > > > > > > > Source files: > > > > > https://people.apache.org/~symat/zookeeper-3.6.4-rc0/ > > > > > > > > > > Maven staging repo: > > > > > > > > > > > > > > > > > > > > https://repository.apache.org/content/groups/staging/org/apache/zookeeper/zookeeper/3.6.4/ > > > > > > > > > > The release candidate
Re: [VOTE] Apache ZooKeeper release 3.6.4 candidate 0
Does the build/test pipeline need to be updated to verify this? Why make it a manual/release step. Patrick On Thu, Dec 15, 2022 at 3:35 PM Szalay-Bekő Máté wrote: > Thanks for checking! > > I don't have a strong opinion. It would make sense to support newer gcc > versions in a new release. On the other hand, it is not a regression on the > branch-3.6 (the c-client in this rc compiles with the same gcc versions > which were compatible with 3.6 3). > > But I am OK to make a new RC. I don't have new gcc installed though to test > it locally. Also, I wonder if installing a new gcc is enough, or the > openssl or other library versions also matter? > > Could you maybe check if the current branch-3.6 compiles on your machine, > with gcc 12.2.0? As you mentioned, the fix for ZOOKEEPER-4641 is already > present there (I merged it after RC 0). If it works for you, then I can add > this commit and cut RC 1. > > Unless someone disagree... > > Thanks, > Máté > > > On Thu, Dec 15, 2022, 6:45 PM Chris Nauroth wrote: > > > Unfortunately, I can't compile the C client because of the FIPS_mode bug > > (ZOOKEEPER-4641). I'm on a newer version of GCC: 12.2.0. I see that > > ZOOKEEPER-4641 was committed to branch-3.6 with a fix version of 3.6.5. > > However, we're intending that 3.6.4 is the final 3.6 release, so there > > never will be a 3.6.5. > > > > Sorry for the churn, but I'd prefer if we could bring that fix into a new > > release candidate. Let me know your thoughts on it. > > > > Chris Nauroth > > > > > > On Wed, Dec 14, 2022 at 4:08 PM Szalay-Bekő Máté < > > szalay.beko.m...@gmail.com> > > wrote: > > > > > +1 (binding) > > > > > > I did the following tests for the release candidate: > > > - verified checksum and gpg signature of the artifacts > > > - I built the source code (incl. the C-client, using -Pfull-build) on > > > Ubuntu 20.04.5 using OpenJDK 8u352, maven 3.6.3 and GCC version 9.4.0 > > > - all the unit tests passed (both Java and C-client) > > > - I also built and executed unit tests for zkpython > > > - I also built the java code (without -Pfull-build) using other JDK > > > versions: 11.0.15, 17.0.3, 18.0.1, 19.0.1 (but didn't run the tests > this > > > time, just used 'clean install -DskipTests') > > > - checkstyle and spotbugs passed > > > - apache-rat passed > > > - owasp (CVE check) passed > > > - fatjar built > > > - I executed quick rolling-upgrade tests (using > > > https://github.com/symat/zk-rolling-upgrade-test): > > > - rolling upgrade from 3.5.10 to 3.6.4 > > > - rolling upgrade from 3.6.3 to 3.6.4 > > > - rolling upgrade from 3.6.4 to 3.7.1 > > > - rolling upgrade from 3.6.4 to 3.8.0 > > > - checked the generated documentation (zookeeper-docs/target/html) > > > - compared generated release notes (releasenotes.html) with Jira ( > > > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310801=12350076 > > > ) > > > > > > Best regards, > > > Máté > > > > > > On Thu, Dec 15, 2022 at 1:05 AM Szalay-Bekő Máté < > > > szalay.beko.m...@gmail.com> > > > wrote: > > > > > > > This is a bugfix release candidate for 3.6.4. It fixes 40 issues, > > > > including CVE fixes, > > > > log4j1 removal (using reload4j from now) and various other bug fixes > > > > (thread leaks, data > > > > corruption, snapshotting and SASL related fixes). > > > > > > > > Please note, that based on our Release Strategy ( > > > > https://zookeeper.apache.org/releases.html#release-strategy) branch > > 3.6 > > > > should become end-of-life and most likely 3.6.4 will be our last 3.6 > > > > release. > > > > > > > > The full release notes is available at: > > > > > > > > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310801=12350076 > > > > > > > > *** Please download, test and vote by December 23th 2022, 23:59 > UTC+0. > > > *** > > > > > > > > > > > > Source files: > > > > https://people.apache.org/~symat/zookeeper-3.6.4-rc0/ > > > > > > > > Maven staging repo: > > > > > > > > > > > > > > https://repository.apache.org/content/groups/staging/org/apache/zookeeper/zookeeper/3.6.4/ > > > > > > > > The release candidate tag in git to be voted upon: release-3.6.4-0 > > > > (please note, branch-3.6.4 will move here only after the vote) > > > > > > > > ZooKeeper's KEYS file containing PGP keys we use to sign the release: > > > > https://www.apache.org/dist/zookeeper/KEYS > > > > > > > > The staging version of the website is: > > > > https://people.apache.org/~symat/zookeeper-3.6.4-rc0/webpage/ > > > > > > > > > > > > Should we release this candidate? > > > > > > > > > > > > Best regards, > > > > Máté > > > > > > > > > >
Re: [VOTE] Apache ZooKeeper release 3.6.4 candidate 0
Thanks for checking! I don't have a strong opinion. It would make sense to support newer gcc versions in a new release. On the other hand, it is not a regression on the branch-3.6 (the c-client in this rc compiles with the same gcc versions which were compatible with 3.6 3). But I am OK to make a new RC. I don't have new gcc installed though to test it locally. Also, I wonder if installing a new gcc is enough, or the openssl or other library versions also matter? Could you maybe check if the current branch-3.6 compiles on your machine, with gcc 12.2.0? As you mentioned, the fix for ZOOKEEPER-4641 is already present there (I merged it after RC 0). If it works for you, then I can add this commit and cut RC 1. Unless someone disagree... Thanks, Máté On Thu, Dec 15, 2022, 6:45 PM Chris Nauroth wrote: > Unfortunately, I can't compile the C client because of the FIPS_mode bug > (ZOOKEEPER-4641). I'm on a newer version of GCC: 12.2.0. I see that > ZOOKEEPER-4641 was committed to branch-3.6 with a fix version of 3.6.5. > However, we're intending that 3.6.4 is the final 3.6 release, so there > never will be a 3.6.5. > > Sorry for the churn, but I'd prefer if we could bring that fix into a new > release candidate. Let me know your thoughts on it. > > Chris Nauroth > > > On Wed, Dec 14, 2022 at 4:08 PM Szalay-Bekő Máté < > szalay.beko.m...@gmail.com> > wrote: > > > +1 (binding) > > > > I did the following tests for the release candidate: > > - verified checksum and gpg signature of the artifacts > > - I built the source code (incl. the C-client, using -Pfull-build) on > > Ubuntu 20.04.5 using OpenJDK 8u352, maven 3.6.3 and GCC version 9.4.0 > > - all the unit tests passed (both Java and C-client) > > - I also built and executed unit tests for zkpython > > - I also built the java code (without -Pfull-build) using other JDK > > versions: 11.0.15, 17.0.3, 18.0.1, 19.0.1 (but didn't run the tests this > > time, just used 'clean install -DskipTests') > > - checkstyle and spotbugs passed > > - apache-rat passed > > - owasp (CVE check) passed > > - fatjar built > > - I executed quick rolling-upgrade tests (using > > https://github.com/symat/zk-rolling-upgrade-test): > > - rolling upgrade from 3.5.10 to 3.6.4 > > - rolling upgrade from 3.6.3 to 3.6.4 > > - rolling upgrade from 3.6.4 to 3.7.1 > > - rolling upgrade from 3.6.4 to 3.8.0 > > - checked the generated documentation (zookeeper-docs/target/html) > > - compared generated release notes (releasenotes.html) with Jira ( > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310801=12350076 > > ) > > > > Best regards, > > Máté > > > > On Thu, Dec 15, 2022 at 1:05 AM Szalay-Bekő Máté < > > szalay.beko.m...@gmail.com> > > wrote: > > > > > This is a bugfix release candidate for 3.6.4. It fixes 40 issues, > > > including CVE fixes, > > > log4j1 removal (using reload4j from now) and various other bug fixes > > > (thread leaks, data > > > corruption, snapshotting and SASL related fixes). > > > > > > Please note, that based on our Release Strategy ( > > > https://zookeeper.apache.org/releases.html#release-strategy) branch > 3.6 > > > should become end-of-life and most likely 3.6.4 will be our last 3.6 > > > release. > > > > > > The full release notes is available at: > > > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310801=12350076 > > > > > > *** Please download, test and vote by December 23th 2022, 23:59 UTC+0. > > *** > > > > > > > > > Source files: > > > https://people.apache.org/~symat/zookeeper-3.6.4-rc0/ > > > > > > Maven staging repo: > > > > > > > > > https://repository.apache.org/content/groups/staging/org/apache/zookeeper/zookeeper/3.6.4/ > > > > > > The release candidate tag in git to be voted upon: release-3.6.4-0 > > > (please note, branch-3.6.4 will move here only after the vote) > > > > > > ZooKeeper's KEYS file containing PGP keys we use to sign the release: > > > https://www.apache.org/dist/zookeeper/KEYS > > > > > > The staging version of the website is: > > > https://people.apache.org/~symat/zookeeper-3.6.4-rc0/webpage/ > > > > > > > > > Should we release this candidate? > > > > > > > > > Best regards, > > > Máté > > > > > >
Re: [EXTERNAL]ZooKeeper 3.6.4 Release Date - EoL for 3.6 after 3.6.4?
Hello Team, We really appreciate the work to release 3.6.4 as we have been waiting for it for some time (due to reload4j changes). But at the same time, we were surprised to hear that 3.6.x is going to be EOL. As per Maven Central https://mvnrepository.com/artifact/org.apache.zookeeper/zookeeper, 3.7.x and 3.8.x versions are relatively less adopted. Also, a lot of Apache projects are still using ZK 3.6.x or older. As we use these projects in our big data clusters, upgrading to 3.7.x may get difficult due to this. AppsZK client version in OSS trunk Hadoop 3.6.3 https://github.com/apache/hadoop/blob/trunk/hadoop-project/pom.xml#L100 Spark 3.6.2 https://github.com/apache/spark/blob/master/pom.xml#L129 Hive3.5.5 https://github.com/apache/hive/blob/master/pom.xml#L208 Presto 3.4.14 https://github.com/prestodb/presto/blob/master/pom.xml#L1870 HBase 3.5.7 https://github.com/apache/hbase/blob/master/pom.xml#L831 Sqoop 3.4.6 https://github.com/apache/sqoop/blob/trunk/gradle.properties#L26 Pig 3.5.7 https://github.com/apache/pig/blob/trunk/ivy/libraries.properties#L74 Ranger 3.4.14 https://github.com/apache/ranger/blob/master/pom.xml#L208 Giraph 3.4.5 https://github.com/apache/giraph/blob/trunk/pom.xml#L355 Hama3.4.5 https://github.com/apache/hama/blob/master/pom.xml#L102 I understand that maintaining an older release is time consuming, but just wanted to provide this data highlighting the existing usage of 3.6.x branch to make sure we make the right trade-offs. Thanks, Dhananjay CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe. Thank you for taking care of Jetty!! I'll run CVE checks and also go through all the important dependencies, bumping them if needed. Máté On Tue, Dec 6, 2022 at 7:00 PM Chris Nauroth wrote: > I would like to get this Jetty dependency upgrade into 3.6.4: > > https://github.com/apache/zookeeper/pull/1941 > > This may be a good time to look at locking in any other relevant dependency > upgrades, as we're considering this to be the last 3.6 release. > > Chris Nauroth > > > On Mon, Dec 5, 2022 at 9:14 AM Chris Nauroth wrote: > > > +1 for retiring the 3.6 release line after 3.6.4. > > > > Máté, thank you for helping with the release! > > > > Chris Nauroth > > > > > > On Sat, Dec 3, 2022 at 10:21 AM Enrico Olivelli > > wrote: > > > >> Mate, > >> > >> Il Sab 3 Dic 2022, 16:53 Szalay-Bekő Máté > ha > >> scritto: > >> > >> > Hello! > >> > > >> > I think I can spare the time for starting the release process sometime > >> in > >> > the second part of next week. > >> > > >> > >> Thanks! I will test it and VOTE > >> > >> > >> > >> > I see the last 3.6 release happened on 13 April, 2021 - pretty long > ago. > >> > There are plenty of tickets to ship, including the log4j -> reload4j > >> > migration: https://issues.apache.org/jira/browse/ZOOKEEPER-4455 > >> > >> > >> > >> This is very important > >> > >> > > >> > > >> > All tickets with fixVersion=3.6.4: > >> > > >> > > >> > https://issues.apache.org/jira/browse/ZOOKEEPER-4602?jql=project%20%3D%20ZOOKEEPER%20AND%20fixVersion%20%3D%203.6.4%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC > >> > > >> > Reading our official release strategy ( > >> > https://zookeeper.apache.org/releases.html), I am not exactly sure > if / > >> > when we should move branch 3.6 to EoL. Maybe after 3.6.4? > >> > > >> > What do you think? > >> > > >> > >> > >> I agree. > >> The migration from 3.6.x to 3.8.x is pretty straightforward and anybody > >> who > >> is on 3.6 should be able to move to 3.8 pretty easily. > >> > >> There is no big reason to maintain the 3.6 branch > >> > >> Thanks for bringing up this discussion > >> > >> Enrico > >> > >> > >> > Máté > >> > > >> > > >> > On Thu, Dec 1, 2022 at 3:31 PM Enrico Olivelli > >> > wrote: > >> > > >> > > Mark > >> > > > >> > > Il giorno sab 26 nov 2022 alle ore 17:57 Mark Sangster > >> > > ha scritto: > >> > > > > >> > > > Hi, > >> > > > > >> > > > Is there a planned release date for 3.6.4? > >> > > > >> > > Currently there is no plan. > >> > > but if there is someone who needs it I believe that we can bootstrap > >> > > the process. > >> > > > >> > > It is only a matter of finding a volunteer to cut the release. > >> > > > >> > > Anyone is willing to help here ? > >> > > > >> > > Enrico > >> > > > >> > > > > >> > > > Mark > >> > > > >> > > >> > > >
Re: Grafana dashboard N/A
Hello Nicolas, Thank you for reporting this. I think this is the correct link: https://grafana.com/grafana/dashboards/10465-zookeeper-by-prometheus/ I filed an issue to track this: https://issues.apache.org/jira/browse/ZOOKEEPER-4653 Are you interested in providing a patch? If so, please feel free to send a pull request to: https://github.com/apache/zookeeper You'll also need an Apache JIRA account. If you don't already have one, you can get one by sending an email to priv...@zookeeper.apache.org with the following information: - email address - preferred username (N.B. hyphens not allowed) - alternate username (in case the preferred one is already in use) - display name, if it is different from the username Chris Nauroth On Thu, Dec 15, 2022 at 1:22 PM Nicolas Parducci wrote: > Hi, > > While looking at documentation I found the Grafana dashboard link N/A at > > https://github.com/apache/zookeeper/blob/master/zookeeper-docs/src/main/resources/markdown/zookeeperMonitor.md > > Linking currently to: https://grafana.com/dashboards/10465 > > Regards, > > Nicolas Parducci >
[jira] [Created] (ZOOKEEPER-4653) Metrics documentation link to Grafana dashboard template is incorrect.
Chris Nauroth created ZOOKEEPER-4653: Summary: Metrics documentation link to Grafana dashboard template is incorrect. Key: ZOOKEEPER-4653 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-4653 Project: ZooKeeper Issue Type: Improvement Components: documentation Reporter: Chris Nauroth This page contains metrics documentation: https://github.com/apache/zookeeper/blob/master/zookeeper-docs/src/main/resources/markdown/zookeeperMonitor.md It includes a link to a Grafana dashboard template, but it goes to a 404: https://grafana.com/dashboards/10465 I think the correct link is this: https://grafana.com/grafana/dashboards/10465-zookeeper-by-prometheus/ -- This message was sent by Atlassian Jira (v8.20.10#820010)
Grafana dashboard N/A
Hi, While looking at documentation I found the Grafana dashboard link N/A at https://github.com/apache/zookeeper/blob/master/zookeeper-docs/src/main/resources/markdown/zookeeperMonitor.md Linking currently to: https://grafana.com/dashboards/10465 Regards, Nicolas Parducci
Re: [VOTE] Apache ZooKeeper release 3.6.4 candidate 0
Unfortunately, I can't compile the C client because of the FIPS_mode bug (ZOOKEEPER-4641). I'm on a newer version of GCC: 12.2.0. I see that ZOOKEEPER-4641 was committed to branch-3.6 with a fix version of 3.6.5. However, we're intending that 3.6.4 is the final 3.6 release, so there never will be a 3.6.5. Sorry for the churn, but I'd prefer if we could bring that fix into a new release candidate. Let me know your thoughts on it. Chris Nauroth On Wed, Dec 14, 2022 at 4:08 PM Szalay-Bekő Máté wrote: > +1 (binding) > > I did the following tests for the release candidate: > - verified checksum and gpg signature of the artifacts > - I built the source code (incl. the C-client, using -Pfull-build) on > Ubuntu 20.04.5 using OpenJDK 8u352, maven 3.6.3 and GCC version 9.4.0 > - all the unit tests passed (both Java and C-client) > - I also built and executed unit tests for zkpython > - I also built the java code (without -Pfull-build) using other JDK > versions: 11.0.15, 17.0.3, 18.0.1, 19.0.1 (but didn't run the tests this > time, just used 'clean install -DskipTests') > - checkstyle and spotbugs passed > - apache-rat passed > - owasp (CVE check) passed > - fatjar built > - I executed quick rolling-upgrade tests (using > https://github.com/symat/zk-rolling-upgrade-test): > - rolling upgrade from 3.5.10 to 3.6.4 > - rolling upgrade from 3.6.3 to 3.6.4 > - rolling upgrade from 3.6.4 to 3.7.1 > - rolling upgrade from 3.6.4 to 3.8.0 > - checked the generated documentation (zookeeper-docs/target/html) > - compared generated release notes (releasenotes.html) with Jira ( > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310801=12350076 > ) > > Best regards, > Máté > > On Thu, Dec 15, 2022 at 1:05 AM Szalay-Bekő Máté < > szalay.beko.m...@gmail.com> > wrote: > > > This is a bugfix release candidate for 3.6.4. It fixes 40 issues, > > including CVE fixes, > > log4j1 removal (using reload4j from now) and various other bug fixes > > (thread leaks, data > > corruption, snapshotting and SASL related fixes). > > > > Please note, that based on our Release Strategy ( > > https://zookeeper.apache.org/releases.html#release-strategy) branch 3.6 > > should become end-of-life and most likely 3.6.4 will be our last 3.6 > > release. > > > > The full release notes is available at: > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310801=12350076 > > > > *** Please download, test and vote by December 23th 2022, 23:59 UTC+0. > *** > > > > > > Source files: > > https://people.apache.org/~symat/zookeeper-3.6.4-rc0/ > > > > Maven staging repo: > > > > > https://repository.apache.org/content/groups/staging/org/apache/zookeeper/zookeeper/3.6.4/ > > > > The release candidate tag in git to be voted upon: release-3.6.4-0 > > (please note, branch-3.6.4 will move here only after the vote) > > > > ZooKeeper's KEYS file containing PGP keys we use to sign the release: > > https://www.apache.org/dist/zookeeper/KEYS > > > > The staging version of the website is: > > https://people.apache.org/~symat/zookeeper-3.6.4-rc0/webpage/ > > > > > > Should we release this candidate? > > > > > > Best regards, > > Máté > > >
