[jira] [Assigned] (ZOOKEEPER-3023) Flaky test: org.apache.zookeeper.server.quorum.Zab1_0Test.testNormalFollowerRunWithDiff

[ https://issues.apache.org/jira/browse/ZOOKEEPER-3023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kezhu Wang reassigned ZOOKEEPER-3023: - Assignee: Kezhu Wang > Flaky test: >

[jira] [Commented] (ZOOKEEPER-4503) A restarted node can be accessed before it finishing synchronization with leader

[ https://issues.apache.org/jira/browse/ZOOKEEPER-4503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17516203#comment-17516203 ] May commented on ZOOKEEPER-4503: Hello [~symat], I updated the bug report and uploaded the logs. > A

[jira] [Updated] (ZOOKEEPER-4503) A restarted node can be accessed before it finishing synchronization with leader

[ https://issues.apache.org/jira/browse/ZOOKEEPER-4503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] May updated ZOOKEEPER-4503: --- Description: Here is the bug triggering process:   # A cluster with three nodes: zk1, zk2 and zk3. zk3

[jira] [Updated] (ZOOKEEPER-4503) A restarted node can be accessed before it finishing synchronization with leader

[ https://issues.apache.org/jira/browse/ZOOKEEPER-4503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] May updated ZOOKEEPER-4503: --- Attachment: zookeeper--server-C1ZK1.out zookeeper--server-C1ZK2.out

[jira] [Updated] (ZOOKEEPER-4503) A restarted node can be accessed before it finishing synchronization with leader

[ https://issues.apache.org/jira/browse/ZOOKEEPER-4503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] May updated ZOOKEEPER-4503: --- Description: Here is the bug triggering process:   # A cluster with three nodes: zk1, zk2 and zk3. zk3

[jira] [Updated] (ZOOKEEPER-4503) A restarted node can be accessed before it finishing synchronization with leader

[ https://issues.apache.org/jira/browse/ZOOKEEPER-4503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] May updated ZOOKEEPER-4503: --- Description: Here is the bug triggering process:   # A cluster with three nodes: zk1, zk2 and zk3. zk3

[jira] [Updated] (ZOOKEEPER-4503) A restarted node can be accessed before it finishing synchronization with leader

[ https://issues.apache.org/jira/browse/ZOOKEEPER-4503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] May updated ZOOKEEPER-4503: --- Description: Here is the bug triggering process:   # A cluster with three nodes: zk1, zk2 and zk3. zk3

[jira] [Updated] (ZOOKEEPER-4503) A restarted node can be accessed before it finishing synchronization with leader

[ https://issues.apache.org/jira/browse/ZOOKEEPER-4503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] May updated ZOOKEEPER-4503: --- Description: Here is the bug triggering process:   # A cluster with three nodes: zk1, zk2 and zk3. zk3

[jira] [Commented] (ZOOKEEPER-4509) log4j vulnerability

[ https://issues.apache.org/jira/browse/ZOOKEEPER-4509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17515820#comment-17515820 ] Adarsh Shukla commented on ZOOKEEPER-4509: -- Thank you Team   Regards, Adarsh > log4j

[jira] [Updated] (ZOOKEEPER-4509) log4j vulnerability

[ https://issues.apache.org/jira/browse/ZOOKEEPER-4509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adarsh Shukla updated ZOOKEEPER-4509: - Affects Version/s: 3.7.0 > log4j vulnerability > --- > >

[jira] [Updated] (ZOOKEEPER-4508) ZooKeeper client run to endless loop in ClientCnxn.SendThread.run if all server down

[ https://issues.apache.org/jira/browse/ZOOKEEPER-4508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated ZOOKEEPER-4508: -- Labels: pull-request-available (was: ) > ZooKeeper client run to endless loop in

[jira] [Resolved] (ZOOKEEPER-4509) log4j vulnerability

[ https://issues.apache.org/jira/browse/ZOOKEEPER-4509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher Tubbs resolved ZOOKEEPER-4509. -- Resolution: Information Provided > log4j vulnerability >

[jira] [Commented] (ZOOKEEPER-4509) log4j vulnerability

[ https://issues.apache.org/jira/browse/ZOOKEEPER-4509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17515814#comment-17515814 ] Christopher Tubbs commented on ZOOKEEPER-4509: -- Which log4j vulnerability? ZooKeeper has

[jira] [Created] (ZOOKEEPER-4509) log4j vulnerability

Adarsh Shukla created ZOOKEEPER-4509: Summary: log4j vulnerability Key: ZOOKEEPER-4509 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-4509 Project: ZooKeeper Issue Type: Bug

[jira] [Assigned] (ZOOKEEPER-4508) ZooKeeper client run to endless loop in ClientCnxn.SendThread.run if all server down

[ https://issues.apache.org/jira/browse/ZOOKEEPER-4508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kezhu Wang reassigned ZOOKEEPER-4508: - Assignee: Kezhu Wang > ZooKeeper client run to endless loop in

[jira] [Created] (ZOOKEEPER-4508) ZooKeeper client run to endless loop in ClientCnxn.SendThread.run if all server down

Kezhu Wang created ZOOKEEPER-4508: - Summary: ZooKeeper client run to endless loop in ClientCnxn.SendThread.run if all server down Key: ZOOKEEPER-4508 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-4508

[jira] [Resolved] (ZOOKEEPER-4490) Publish Clover results to SonarQube

[ https://issues.apache.org/jira/browse/ZOOKEEPER-4490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mate Szalay-Beko resolved ZOOKEEPER-4490. - Resolution: Done > Publish Clover results to SonarQube >

[jira] [Updated] (ZOOKEEPER-4490) Publish Clover results to SonarQube

[ https://issues.apache.org/jira/browse/ZOOKEEPER-4490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mate Szalay-Beko updated ZOOKEEPER-4490: Fix Version/s: 3.9.0 > Publish Clover results to SonarQube >