[GitHub] zookeeper pull request #587: ZOOKEEPER-3106: Zookeeper client supports IPv6 ...

2018-08-01 Thread maoling
Github user maoling commented on a diff in the pull request: https://github.com/apache/zookeeper/pull/587#discussion_r207090394 --- Diff: src/java/main/org/apache/zookeeper/client/ConnectStringParser.java --- @@ -68,14 +69,26 @@ public ConnectStringParser(String connectString) {

[jira] [Commented] (ZOOKEEPER-3062) introduce fsync.warningthresholdms constant for FileTxnLog LOG.warn message

2018-08-01 Thread Hudson (JIRA)
[ https://issues.apache.org/jira/browse/ZOOKEEPER-3062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16566277#comment-16566277 ] Hudson commented on ZOOKEEPER-3062: --- SUCCESS: Integrated in Jenkins build ZooKeeper-trunk #131 (See

ZooKeeper_branch35_jdk8 - Build # 1068 - Failure

2018-08-01 Thread Apache Jenkins Server
See https://builds.apache.org/job/ZooKeeper_branch35_jdk8/1068/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 62.63 KB...] [junit] Running

[GitHub] zookeeper pull request #588: [ZOOKEEPER-3109] Avoid long unavailable time du...

2018-08-01 Thread lvfangmin
GitHub user lvfangmin opened a pull request: https://github.com/apache/zookeeper/pull/588 [ZOOKEEPER-3109] Avoid long unavailable time due to voter changed mind during leader election For more details, please check descriptions in

[jira] [Updated] (ZOOKEEPER-3109) Avoid long unavailable time due to voter changed mind when activating the leader during election

2018-08-01 Thread ASF GitHub Bot (JIRA)
[ https://issues.apache.org/jira/browse/ZOOKEEPER-3109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated ZOOKEEPER-3109: -- Labels: pull-request-available (was: ) > Avoid long unavailable time due to voter

[jira] [Created] (ZOOKEEPER-3109) Avoid long unavailable time due to voter changed mind when activating the leader during election

2018-08-01 Thread Fangmin Lv (JIRA)
Fangmin Lv created ZOOKEEPER-3109: - Summary: Avoid long unavailable time due to voter changed mind when activating the leader during election Key: ZOOKEEPER-3109 URL:

[jira] [Updated] (ZOOKEEPER-3109) Avoid long unavailable time due to voter changed mind when activating the leader during election

2018-08-01 Thread Fangmin Lv (JIRA)
[ https://issues.apache.org/jira/browse/ZOOKEEPER-3109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fangmin Lv updated ZOOKEEPER-3109: -- Description: Occasionally, we'll find it takes long time to elect a leader, might longer

Re: Test failures (SASL) with Java 11 - any ideas?

2018-08-01 Thread Enrico Olivelli
Il mer 1 ago 2018, 21:08 Patrick Hunt ha scritto: > We had discussed dropping java6 as a supported platform recently. Perhaps > yet another reason to move forward with that? > So if we drop java6 we can use kerby. It shouldn't be difficult, just port 3.5 branch config. Don't know if it possible

[jira] [Commented] (ZOOKEEPER-3082) Fix server snapshot behavior when out of disk space

2018-08-01 Thread Brian Nixon (JIRA)
[ https://issues.apache.org/jira/browse/ZOOKEEPER-3082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16565860#comment-16565860 ] Brian Nixon commented on ZOOKEEPER-3082: [~andorm] my (possibly incorrect) read on

[GitHub] zookeeper issue #566: ZOOKEEPER-3062: mention fsync.warningthresholdms in Fi...

2018-08-01 Thread phunt
Github user phunt commented on the issue: https://github.com/apache/zookeeper/pull/566 lgtm. +1, thanks @cpoerschke . Perhaps consider logging the value during startup (initial read of the value) instead? ---

[jira] [Resolved] (ZOOKEEPER-3062) mention fsync.warningthresholdms in FileTxnLog LOG.warn message

2018-08-01 Thread Patrick Hunt (JIRA)
[ https://issues.apache.org/jira/browse/ZOOKEEPER-3062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt resolved ZOOKEEPER-3062. - Resolution: Fixed Hadoop Flags: Reviewed LGTM. Thanks [~cpoerschke]! >

[jira] [Updated] (ZOOKEEPER-3062) introduce fsync.warningthresholdms constant for FileTxnLog LOG.warn message

2018-08-01 Thread Patrick Hunt (JIRA)
[ https://issues.apache.org/jira/browse/ZOOKEEPER-3062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-3062: Summary: introduce fsync.warningthresholdms constant for FileTxnLog LOG.warn message

[jira] [Updated] (ZOOKEEPER-3062) mention fsync.warningthresholdms in FileTxnLog LOG.warn message

2018-08-01 Thread Patrick Hunt (JIRA)
[ https://issues.apache.org/jira/browse/ZOOKEEPER-3062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-3062: Fix Version/s: 3.4.14 3.5.5 3.6.0 > mention

[jira] [Updated] (ZOOKEEPER-3062) mention fsync.warningthresholdms in FileTxnLog LOG.warn message

2018-08-01 Thread Patrick Hunt (JIRA)
[ https://issues.apache.org/jira/browse/ZOOKEEPER-3062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-3062: Affects Version/s: 3.6.0 3.5.4 3.4.13 >

[jira] [Assigned] (ZOOKEEPER-3062) mention fsync.warningthresholdms in FileTxnLog LOG.warn message

2018-08-01 Thread Patrick Hunt (JIRA)
[ https://issues.apache.org/jira/browse/ZOOKEEPER-3062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt reassigned ZOOKEEPER-3062: --- Assignee: Christine Poerschke > mention fsync.warningthresholdms in FileTxnLog

[GitHub] zookeeper pull request #566: ZOOKEEPER-3062: mention fsync.warningthresholdm...

2018-08-01 Thread asfgit
Github user asfgit closed the pull request at: https://github.com/apache/zookeeper/pull/566 ---

Re: Trying to find pattern in Flaky Tests

2018-08-01 Thread Patrick Hunt
Looks like 16808 has been resolved - I haven't noticed it after the recent changes. Note that INFRA recently added openjdk10 to Jenkins and I added a job or two which seem to be working OK. Java 11 is failing on 3.4 due to broken libraries (according to Rakesh on another thread) but we're also

Re: Test failures (SASL) with Java 11 - any ideas?

2018-08-01 Thread Patrick Hunt
We had discussed dropping java6 as a supported platform recently. Perhaps yet another reason to move forward with that? Patrick On Sun, Jul 22, 2018 at 8:13 PM Rakesh Radhakrishnan wrote: > Do you know why 3.4 is not using kerby? > > In short, Kerby was failing with java-6. Please refer

[jira] [Commented] (ZOOKEEPER-3108) deprecated myid file and use a new property "server.id" in the zoo.cfg

2018-08-01 Thread Brian Nixon (JIRA)
[ https://issues.apache.org/jira/browse/ZOOKEEPER-3108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16565814#comment-16565814 ] Brian Nixon commented on ZOOKEEPER-3108: This seems like a good idea to me (provided myid

[GitHub] zookeeper pull request #587: ZOOKEEPER-3106: Zookeeper client supports IPv6 ...

2018-08-01 Thread enixon
Github user enixon commented on a diff in the pull request: https://github.com/apache/zookeeper/pull/587#discussion_r206983579 --- Diff: src/java/main/org/apache/zookeeper/client/ConnectStringParser.java --- @@ -68,14 +69,26 @@ public ConnectStringParser(String connectString) {

[GitHub] zookeeper pull request #587: ZOOKEEPER-3106: Zookeeper client supports IPv6 ...

2018-08-01 Thread enixon
Github user enixon commented on a diff in the pull request: https://github.com/apache/zookeeper/pull/587#discussion_r206987004 --- Diff: src/java/main/org/apache/zookeeper/client/ConnectStringParser.java --- @@ -68,14 +69,26 @@ public ConnectStringParser(String connectString) {

[GitHub] zookeeper pull request #:

2018-08-01 Thread maoling
Github user maoling commented on the pull request: https://github.com/apache/zookeeper/commit/a2623a625a4778720f7d5482d0a66e9b37ae556f#commitcomment-29922823 @nkalmar Thanks for your nice explain. these security problems can also exist in the JMX and Jetty? ---

[GitHub] zookeeper pull request #:

2018-08-01 Thread nkalmar
Github user nkalmar commented on the pull request: https://github.com/apache/zookeeper/commit/a2623a625a4778720f7d5482d0a66e9b37ae556f#commitcomment-29917129 @maoling , the problem is, there is no security implemented. Anyone user who can access ZooKeeper, can send commands to the