[jira] [Updated] (ZOOKEEPER-3211) zookeeper standalone mode，found a high level bug in kernel of centos7.0 ，zookeeper Server's tcp/ip socket connections(default 60 ) are CLOSE_WAIT ，this lead to zk ca

[ https://issues.apache.org/jira/browse/ZOOKEEPER-3211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yeshuangshuang updated ZOOKEEPER-3211: -- Attachment: 2018-12-09_133320.png 2018-12-09_133248.png

[jira] [Updated] (ZOOKEEPER-3211) zookeeper standalone mode，found a high level bug in kernel of centos7.0 ，zookeeper Server's tcp/ip socket connections(default 60 ) are CLOSE_WAIT ，this lead to zk ca

[ https://issues.apache.org/jira/browse/ZOOKEEPER-3211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yeshuangshuang updated ZOOKEEPER-3211: -- Attachment: (was: zklog.rar) > zookeeper standalone mode，found a high level

[jira] [Commented] (ZOOKEEPER-3211) zookeeper standalone mode，found a high level bug in kernel of centos7.0 ，zookeeper Server's tcp/ip socket connections(default 60 ) are CLOSE_WAIT ，this lead to zk

[ https://issues.apache.org/jira/browse/ZOOKEEPER-3211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16719845#comment-16719845 ] yeshuangshuang commented on ZOOKEEPER-3211: --- 27/5000 * increase your limit

[jira] [Commented] (ZOOKEEPER-3180) Add response cache to improve the throughput of read heavy traffic

[ https://issues.apache.org/jira/browse/ZOOKEEPER-3180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16719752#comment-16719752 ] Michael Han commented on ZOOKEEPER-3180: My experience with JVM GC and ZooKeeper is GC is

Re: Migrating ZooKeeper to GitBox

+1 on voluntarily request to move. On Wed, Dec 12, 2018 at 11:36 AM Patrick Hunt wrote: > Probably minor, but note there are some website pages that will also need > to be updated: > e.g. https://zookeeper.apache.org/git.html > > Patrick > > On Wed, Dec 12, 2018 at 10:58 AM Enrico Olivelli >

[jira] [Commented] (ZOOKEEPER-3211) zookeeper standalone mode，found a high level bug in kernel of centos7.0 ，zookeeper Server's tcp/ip socket connections(default 60 ) are CLOSE_WAIT ，this lead to zk

[ https://issues.apache.org/jira/browse/ZOOKEEPER-3211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16719736#comment-16719736 ] Michael Han commented on ZOOKEEPER-3211: {quote}Have similar defects been solved in 3.4.13?

[jira] [Commented] (ZOOKEEPER-3211) zookeeper standalone mode，found a high level bug in kernel of centos7.0 ，zookeeper Server's tcp/ip socket connections(default 60 ) are CLOSE_WAIT ，this lead to zk

[ https://issues.apache.org/jira/browse/ZOOKEEPER-3211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16719703#comment-16719703 ] yeshuangshuang commented on ZOOKEEPER-3211: --- I have seen a futex bug in Linux on the

[jira] [Commented] (ZOOKEEPER-3211) zookeeper standalone mode，found a high level bug in kernel of centos7.0 ，zookeeper Server's tcp/ip socket connections(default 60 ) are CLOSE_WAIT ，this lead to zk

[ https://issues.apache.org/jira/browse/ZOOKEEPER-3211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16719699#comment-16719699 ] yeshuangshuang commented on ZOOKEEPER-3211: --- Given the 3.4.5 that has been used in the

Re: Leader election

>> Can we reduce this time by configuring "syncLimit" and "tickTime" to let's say 5 seconds? Can we have a strong guarantee on this time bound? It's not possible to guarantee the time bound, because of FLP impossibility (reliable failure detection is not possible in async environment). Though

[jira] [Commented] (ZOOKEEPER-3211) zookeeper standalone mode，found a high level bug in kernel of centos7.0 ，zookeeper Server's tcp/ip socket connections(default 60 ) are CLOSE_WAIT ，this lead to zk

[ https://issues.apache.org/jira/browse/ZOOKEEPER-3211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16719680#comment-16719680 ] Michael Han commented on ZOOKEEPER-3211: [~yss] Have you tried newer version of stable

[jira] [Commented] (ZOOKEEPER-3214) Flaky test: org.apache.zookeeper.server.quorum.QuorumPeerMainTest.testLeaderElectionWithDisloyalVoter

[ https://issues.apache.org/jira/browse/ZOOKEEPER-3214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16719671#comment-16719671 ] Michael Han commented on ZOOKEEPER-3214: Thanks for reporting the flaky test. It's important

[jira] [Reopened] (ZOOKEEPER-3141) testLeaderElectionWithDisloyalVoter is flaky

[ https://issues.apache.org/jira/browse/ZOOKEEPER-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Han reopened ZOOKEEPER-3141: Reopen this issue because this test was observed similar symptom recently as reported  in

[jira] [Resolved] (ZOOKEEPER-3214) Flaky test: org.apache.zookeeper.server.quorum.QuorumPeerMainTest.testLeaderElectionWithDisloyalVoter

[ https://issues.apache.org/jira/browse/ZOOKEEPER-3214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Han resolved ZOOKEEPER-3214. Resolution: Duplicate > Flaky test: >

[jira] [Created] (ZOOKEEPER-3214) Flaky test: org.apache.zookeeper.server.quorum.QuorumPeerMainTest.testLeaderElectionWithDisloyalVoter

maoling created ZOOKEEPER-3214: -- Summary: Flaky test: org.apache.zookeeper.server.quorum.QuorumPeerMainTest.testLeaderElectionWithDisloyalVoter Key: ZOOKEEPER-3214 URL:

[jira] [Updated] (ZOOKEEPER-3209) New `getEphemerals` api to get all the ephemeral nodes created by the session

[ https://issues.apache.org/jira/browse/ZOOKEEPER-3209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated ZOOKEEPER-3209: -- Labels: features pull-request-available (was: features) > New `getEphemerals` api

[GitHub] zookeeper pull request #735: ZOOKEEPER-3209: New `getEphemerals` api to get ...

GitHub user dineshappavoo opened a pull request: https://github.com/apache/zookeeper/pull/735 ZOOKEEPER-3209: New `getEphemerals` api to get all the ephemeral nodes created by the session See https://issues.apache.org/jira/browse/ZOOKEEPER-3209 for details about the API.

[jira] [Updated] (ZOOKEEPER-3209) New `getEphemerals` api to get all the ephemeral nodes created by the session

[ https://issues.apache.org/jira/browse/ZOOKEEPER-3209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Appavoo updated ZOOKEEPER-3209: -- Summary: New `getEphemerals` api to get all the ephemeral nodes created by the

[GitHub] zookeeper issue #714: Zookeeper 1818 (on branch-3.5)

Github user mkedwards commented on the issue: https://github.com/apache/zookeeper/pull/714 I updated this PR to match the changes made to #703 during review. Anything else I can do to help? ---

[GitHub] zookeeper issue #730: Zookeeper-3188: Improve resilience to network

Github user hanm commented on the issue: https://github.com/apache/zookeeper/pull/730 @ArtemChernatsky I think you need rebase with master first before update your patch. In any case, looks like the number of failed tests are reduced, which is good. ---

[GitHub] zookeeper issue #714: Zookeeper 1818 (on branch-3.5)

Github user anmolnar commented on the issue: https://github.com/apache/zookeeper/pull/714 @mkedwards @lvfangmin Apologies for being pushy, but this is a critical patch for the 3.5 release. Can we move on? ---

Re: Migrating ZooKeeper to GitBox

Probably minor, but note there are some website pages that will also need to be updated: e.g. https://zookeeper.apache.org/git.html Patrick On Wed, Dec 12, 2018 at 10:58 AM Enrico Olivelli wrote: > +1 for moving to github now > > Enrico > > Il mer 12 dic 2018, 19:49 Tamas Penzes ha >

Re: Migrating ZooKeeper to GitBox

+1 for moving to github now Enrico Il mer 12 dic 2018, 19:49 Tamas Penzes ha scritto: > Hi Patrick, > > Yes we have to upgrade the main pom.xml, just as the website and the > documentation. > Do we have to change git urls in old documentations as well? (People might > read them.) > > Thanks,

Re: Migrating ZooKeeper to GitBox

Hi Patrick, Yes we have to upgrade the main pom.xml, just as the website and the documentation. Do we have to change git urls in old documentations as well? (People might read them.) Thanks, Tamaas On Wed, Dec 12, 2018, 18:31 Patrick Hunt Proactive sounds good to me. Can we schedule something

Re: Migrating ZooKeeper to GitBox

Proactive sounds good to me. Can we schedule something outside the holidays? Aside from Jenkins is there anything else we need to worry about? e.g. I see a reference in pom.xml pom.xml 63:scm:git: https://git-wip-us.apache.org/repos/asf/zookeeper.git 64:

Migrating ZooKeeper to GitBox

Hi dev team, Have you seen this? https://blogs.apache.org/infra/entry/relocation-of-apache-git-repositories I think we should volunteer for a coordinated migration of ZooKeeper, although the project is not too big,

ZooKeeper_branch34_openjdk7 - Build # 2150 - Failure

See https://builds.apache.org/job/ZooKeeper_branch34_openjdk7/2150/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 43.50 KB...] [junit] Running

[GitHub] zookeeper issue #728: ZOOKEEPER-3160: Custom User SSLContext

Github user arankin-irl commented on the issue: https://github.com/apache/zookeeper/pull/728 @anmolnar - I've updated the PR with the extracted method. ---

[jira] [Commented] (ZOOKEEPER-3211) zookeeper standalone mode，found a high level bug in kernel of centos7.0 ，zookeeper Server's tcp/ip socket connections(default 60 ) are CLOSE_WAIT ，this lead to zk

[ https://issues.apache.org/jira/browse/ZOOKEEPER-3211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16718889#comment-16718889 ] maoling commented on ZOOKEEPER-3211: interesting,I will test this issue in my docker. [~yss] Do

[jira] [Commented] (ZOOKEEPER-3211) zookeeper standalone mode，found a high level bug in kernel of centos7.0 ，zookeeper Server's tcp/ip socket connections(default 60 ) are CLOSE_WAIT ，this lead to zk

[ https://issues.apache.org/jira/browse/ZOOKEEPER-3211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16718641#comment-16718641 ] yeshuangshuang commented on ZOOKEEPER-3211: --- i've updated > zookeeper standalone

[jira] [Updated] (ZOOKEEPER-3211) zookeeper standalone mode，found a high level bug in kernel of centos7.0 ，zookeeper Server's tcp/ip socket connections(default 60 ) are CLOSE_WAIT ，this lead to zk ca

[ https://issues.apache.org/jira/browse/ZOOKEEPER-3211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yeshuangshuang updated ZOOKEEPER-3211: -- Environment: 1.zoo.cfg server.1=127.0.0.1:2902:2903 2.kernel kernel：Linux