Re: RC1 issues (was: Re: [VOTE] Apache ZooKeeper release 3.5.2-alpha candidate 1)

[Rakesh Radhakrishnan]

>> I'm suggesting as a blocker for 3.5.3, I think we should proceed with
3.5.2 as is and give some love to the C client in the next release.

Since the current release is alpha I also feel its OK to go ahead with RC1
and address the C client issue in 3.5.3. That way we'll get more folks
trying it out and stabilize 3.5 version eventually. Probably will listen to
others opinion as well.

-Rakesh

On Mon, Jul 4, 2016 at 12:32 AM, Flavio Junqueira  wrote:

>
> > On 03 Jul 2016, at 17:53, Chris Nauroth 
> wrote:
> >
> > For my part, I got a successful full test run from RC1 before starting
> the
> > [VOTE].  The problem with the silent failure of multi tests could have
> > snuck past me easily though.  (Flavio, thank you for filing
> > ZOOKEEPER-2463.)  I'm curious to hear test results from others who are
> > trying RC1.
>
> The test failures seem to be related to test timing, not bugs, but I
> haven't been able to confirm for the last two I mentioned. Granted that
> timing is in some sense a bug, all I'm saying is that it doesn't seem to
> indicate a regression or anything.
>
> >
> > It looks like we also need an issue to track updating the copyright
> notice
> > in the docs.  I don't believe this is an ASF compliance problem in the
> > same way that an erroneous NOTICE file would be, so I propose that we
> > address it in 3.5.3.
>
> Agreed, we need an issue for that.
>
> >
> > Flavio, you suggested filing a blocker for the ZooKeeperQuorumServer.cc
> > failure.  Did you want that targeted to 3.5.2 or 3.5.3?
> >
>
> I'm suggesting as a blocker for 3.5.3, I think we should proceed with
> 3.5.2 as is and give some love to the C client in the next release.
>
> > Overall, how are people feeling about the RC1 [VOTE] at this point?  Is
> > anyone considering a -1, or shall we proceed (keeping in mind it's an
> > alpha) with the intent of fixing things in a more rapid 3.5.3 release
> > cycle?
>
> I'd say we proceed.
>
> -Flavio
>
> >
> >
> >
> > On 7/3/16, 8:43 AM, "Flavio Junqueira"  wrote:
> >
> >> The issue with the TestReconfigServer test is that the client port is
> >> still used and we get a bind exception, which prevents the server from
> >> starting. To verify this locally, I simply added some code to retry and
> >> it works fine with that fix. Going forward we need a better fox.
> >>
> >> I haven't able to figure out yet the issue with the
> >> Zookeeper_simpleSystem tests.
> >>
> >> I have also found something strange with the multi tests. I have created
> >> ZK-2463 for this problem and made it a blocker for 3.5.3.
> >>
> >> -Flavio
> >>
> >>> On 03 Jul 2016, at 15:25, Flavio Junqueira  wrote:
> >>>
> >>> I have spun a new ubuntu VM to check the C failures. I get three
> >>> failures with the new installation:
> >>>
> >>> Zookeeper_simpleSystem::testFirstServerDown : assertion : elapsed 10911
> >>> tests/TestClient.cc:411: Assertion: equality assertion failed
> >>> [Expected: -101, Actual  : -4]
> >>> tests/TestClient.cc:322: Assertion: assertion failed [Expression:
> >>> ctx.waitForConnected(zk)]
> >>> Failures !!!
> >>> Run: 43   Failure total: 2   Failures: 2   Errors: 0
> >>>
> >>>
> >>>
> >>> TestReconfigServer::testRemoveFollower/usr/bin/java
> >>> ZooKeeper JMX enabled by default
> >>> Using config: ./../../build/test/test-cppunit/conf/0.conf
> >>> Starting zookeeper ... FAILED TO START
> >>> zktest-mt: tests/ZooKeeperQuorumServer.cc:61: void
> >>> ZooKeeperQuorumServer::start(): Assertion `system(command.c_str()) ==
> 0'
> >>> failed.
> >>> /bin/bash: line 5: 47059 Aborted (core dumped)
> >>> ZKROOT=./../.. CLASSPATH=$CLASSPATH:$CLOVER_HOME/lib/clover.jar
> >>> ${dir}$tst
> >>>
> >>> -Flavio
> >>>
> >>>
>  On 03 Jul 2016, at 15:19, Edward Ribeiro 
>  wrote:
> 
>  Hi Flavio,
> 
> 
>  On Sun, Jul 3, 2016 at 5:54 AM, Flavio Junqueira   > wrote:
>  Hey Eddie,
> 
>  A few comments on your points:
> 
> >
> > - the copyright notice is still dating "2008-2013". It's worth
> > updating to
> > the current year?
> 
>  Where are you seeing this? The NOTICE file is correct from what I can
>  see.
> 
>  ​Ops, sorry. I was referring to the PDFs and HTMLs in the docs/
>  folder. Even after running "ant docs" the footnote has "2008-2013"
>  copyright. Images attached.
> 
> 
> 
> > - I consistently ran on an test error equals to the one at
> > https://builds.apache.org/job/ZooKeeper-trunk/2982/console
> > 
> >  > >
> 
>  I think this is ZK-2152, which Chris has moved to 3.5.3, so even
>  though it isn't ideal. it is expected.
> 
>  ​Got it. :)
>  ​
> 
> > - Also this one:
> >
> >
> https://mail-archives.apache.org/mod_mbox/zookeeper-dev/20

[jira] [Commented] (ZOOKEEPER-1045) Support Quorum Peer mutual authentication via SASL

[Rakesh R (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-1045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15360796#comment-15360796
 ] 

Rakesh R commented on ZOOKEEPER-1045:
-

[~hanm] Yes, exactly. Presently we will be supporting only single(shared) Kerb 
principal across all the servers now. We could capture this point clearly in 
our test report documentation and later the same can be used to update {{cwiki 
page}} as well. In future, if anyone has a use case of different Kerb principal 
then we can discuss/extend the implementation to support the same later. IMHO, 
its not required to handle those complex case now. Does that make sense to you?

> Support Quorum Peer mutual authentication via SASL
> --
>
> Key: ZOOKEEPER-1045
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1045
> Project: ZooKeeper
>  Issue Type: New Feature
>  Components: server
>Reporter: Eugene Koontz
>Assignee: Rakesh R
>Priority: Critical
> Fix For: 3.4.9, 3.5.3
>
> Attachments: 0001-ZOOKEEPER-1045-br-3-4.patch, 
> 1045_failing_phunt.tar.gz, ZK-1045-test-case-failure-logs.zip, 
> ZOOKEEPER-1045-00.patch, ZOOKEEPER-1045-Rolling Upgrade Design Proposal.pdf, 
> ZOOKEEPER-1045-br-3-4.patch, ZOOKEEPER-1045-br-3-4.patch, 
> ZOOKEEPER-1045-br-3-4.patch, ZOOKEEPER-1045-br-3-4.patch, 
> ZOOKEEPER-1045-br-3-4.patch
>
>
> ZOOKEEPER-938 addresses mutual authentication between clients and servers. 
> This bug, on the other hand, is for authentication among quorum peers. 
> Hopefully much of the work done on SASL integration with Zookeeper for 
> ZOOKEEPER-938 can be used as a foundation for this enhancement.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (ZOOKEEPER-1045) Support Quorum Peer mutual authentication via SASL

[Rakesh R (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-1045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15360796#comment-15360796
 ] 

Rakesh R edited comment on ZOOKEEPER-1045 at 7/4/16 3:36 AM:
-

[~hanm] Yes, exactly. Presently we will be supporting only single(shared) Kerb 
principal across all the servers. We could capture this point clearly in our 
test report documentation and later the same can be used to update {{cwiki 
page}} as well. In future, if anyone has a use case of different Kerb principal 
then we can discuss/extend the implementation to support the same later. IMHO, 
its not required to handle those complex case now. Does that make sense to you?


was (Author: rakeshr):
[~hanm] Yes, exactly. Presently we will be supporting only single(shared) Kerb 
principal across all the servers now. We could capture this point clearly in 
our test report documentation and later the same can be used to update {{cwiki 
page}} as well. In future, if anyone has a use case of different Kerb principal 
then we can discuss/extend the implementation to support the same later. IMHO, 
its not required to handle those complex case now. Does that make sense to you?

> Support Quorum Peer mutual authentication via SASL
> --
>
> Key: ZOOKEEPER-1045
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1045
> Project: ZooKeeper
>  Issue Type: New Feature
>  Components: server
>Reporter: Eugene Koontz
>Assignee: Rakesh R
>Priority: Critical
> Fix For: 3.4.9, 3.5.3
>
> Attachments: 0001-ZOOKEEPER-1045-br-3-4.patch, 
> 1045_failing_phunt.tar.gz, ZK-1045-test-case-failure-logs.zip, 
> ZOOKEEPER-1045-00.patch, ZOOKEEPER-1045-Rolling Upgrade Design Proposal.pdf, 
> ZOOKEEPER-1045-br-3-4.patch, ZOOKEEPER-1045-br-3-4.patch, 
> ZOOKEEPER-1045-br-3-4.patch, ZOOKEEPER-1045-br-3-4.patch, 
> ZOOKEEPER-1045-br-3-4.patch
>
>
> ZOOKEEPER-938 addresses mutual authentication between clients and servers. 
> This bug, on the other hand, is for authentication among quorum peers. 
> Hopefully much of the work done on SASL integration with Zookeeper for 
> ZOOKEEPER-938 can be used as a foundation for this enhancement.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (ZOOKEEPER-1045) Support Quorum Peer mutual authentication via SASL

[Michael Han (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-1045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15360675#comment-15360675
 ] 

Michael Han edited comment on ZOOKEEPER-1045 at 7/3/16 8:46 PM:


bq. For the server-server auth, Kerb principal should be same for all the 
servers to allow communicating each other. 

IIUC, this means that we only support a single (shared) Kerberos principal / 
credential across all servers for server to server communication, and if so, 
the failure of my validation against the case where servers use different 
Kerberos principal is a by design, because I was using different Kerberos 
principals on each server for server to server auth validation. [~rakeshr]


was (Author: hanm):
b.q. For the server-server auth, Kerb principal should be same for all the 
servers to allow communicating each other. 

IIUC, this means that we only support a single (shared) Kerberos principal / 
credential across all servers for server to server communication, and if so, 
the failure of my validation against the case where servers use different 
Kerberos principal is a by design, because I was using different Kerberos 
principals on each server for server to server auth validation. [~rakeshr]

> Support Quorum Peer mutual authentication via SASL
> --
>
> Key: ZOOKEEPER-1045
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1045
> Project: ZooKeeper
>  Issue Type: New Feature
>  Components: server
>Reporter: Eugene Koontz
>Assignee: Rakesh R
>Priority: Critical
> Fix For: 3.4.9, 3.5.3
>
> Attachments: 0001-ZOOKEEPER-1045-br-3-4.patch, 
> 1045_failing_phunt.tar.gz, ZK-1045-test-case-failure-logs.zip, 
> ZOOKEEPER-1045-00.patch, ZOOKEEPER-1045-Rolling Upgrade Design Proposal.pdf, 
> ZOOKEEPER-1045-br-3-4.patch, ZOOKEEPER-1045-br-3-4.patch, 
> ZOOKEEPER-1045-br-3-4.patch, ZOOKEEPER-1045-br-3-4.patch, 
> ZOOKEEPER-1045-br-3-4.patch
>
>
> ZOOKEEPER-938 addresses mutual authentication between clients and servers. 
> This bug, on the other hand, is for authentication among quorum peers. 
> Hopefully much of the work done on SASL integration with Zookeeper for 
> ZOOKEEPER-938 can be used as a foundation for this enhancement.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ZOOKEEPER-1045) Support Quorum Peer mutual authentication via SASL

[Michael Han (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-1045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15360675#comment-15360675
 ] 

Michael Han commented on ZOOKEEPER-1045:


b.q. For the server-server auth, Kerb principal should be same for all the 
servers to allow communicating each other. 

IIUC, this means that we only support a single (shared) Kerberos principal / 
credential across all servers for server to server communication, and if so, 
the failure of my validation against the case where servers use different 
Kerberos principal is a by design, because I was using different Kerberos 
principals on each server for server to server auth validation. [~rakeshr]

> Support Quorum Peer mutual authentication via SASL
> --
>
> Key: ZOOKEEPER-1045
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1045
> Project: ZooKeeper
>  Issue Type: New Feature
>  Components: server
>Reporter: Eugene Koontz
>Assignee: Rakesh R
>Priority: Critical
> Fix For: 3.4.9, 3.5.3
>
> Attachments: 0001-ZOOKEEPER-1045-br-3-4.patch, 
> 1045_failing_phunt.tar.gz, ZK-1045-test-case-failure-logs.zip, 
> ZOOKEEPER-1045-00.patch, ZOOKEEPER-1045-Rolling Upgrade Design Proposal.pdf, 
> ZOOKEEPER-1045-br-3-4.patch, ZOOKEEPER-1045-br-3-4.patch, 
> ZOOKEEPER-1045-br-3-4.patch, ZOOKEEPER-1045-br-3-4.patch, 
> ZOOKEEPER-1045-br-3-4.patch
>
>
> ZOOKEEPER-938 addresses mutual authentication between clients and servers. 
> This bug, on the other hand, is for authentication among quorum peers. 
> Hopefully much of the work done on SASL integration with Zookeeper for 
> ZOOKEEPER-938 can be used as a foundation for this enhancement.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ZOOKEEPER-2152) Intermittent failure in TestReconfig.cc

[Michael Han (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15360673#comment-15360673
 ] 

Michael Han commented on ZOOKEEPER-2152:


Agree, updated JIRA. 

> Intermittent failure in TestReconfig.cc
> ---
>
> Key: ZOOKEEPER-2152
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2152
> Project: ZooKeeper
>  Issue Type: Sub-task
>  Components: c client
>Reporter: Michi Mutsuzaki
>Assignee: Michael Han
>  Labels: reconfiguration
> Fix For: 3.5.3, 3.6.0
>
> Attachments: ZOOKEEPER-2152.patch
>
>
> I'm seeing this failure in the c client test once in a while:
> {noformat}
> [exec] 
> /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/trunk/src/c/tests/TestReconfig.cc:474:
>  Assertion: assertion failed [Expression: found != string::npos, 
> 10.10.10.4:2004 not in newComing list]
> {noformat}
> https://builds.apache.org/job/ZooKeeper-trunk/2640/console



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ZOOKEEPER-2080) ReconfigRecoveryTest fails intermittently

[Michael Han (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Han updated ZOOKEEPER-2080:
---
Fix Version/s: 3.6.0
   3.5.3

> ReconfigRecoveryTest fails intermittently
> -
>
> Key: ZOOKEEPER-2080
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2080
> Project: ZooKeeper
>  Issue Type: Sub-task
>Reporter: Ted Yu
>Assignee: Michael Han
> Fix For: 3.5.3, 3.6.0
>
> Attachments: ZOOKEEPER-2080.patch, 
> jacoco-ZOOKEEPER-2080.unzip-grows-to-70MB.7z, repro-20150816.log, 
> threaddump.log
>
>
> I got the following test failure on MacBook with trunk code:
> {code}
> Testcase: testCurrentObserverIsParticipantInNewConfig took 93.628 sec
>   FAILED
> waiting for server 2 being up
> junit.framework.AssertionFailedError: waiting for server 2 being up
>   at 
> org.apache.zookeeper.server.quorum.ReconfigRecoveryTest.testCurrentObserverIsParticipantInNewConfig(ReconfigRecoveryTest.java:529)
>   at 
> org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:52)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ZOOKEEPER-2152) Intermittent failure in TestReconfig.cc

[Michael Han (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Han updated ZOOKEEPER-2152:
---
Fix Version/s: 3.5.3

> Intermittent failure in TestReconfig.cc
> ---
>
> Key: ZOOKEEPER-2152
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2152
> Project: ZooKeeper
>  Issue Type: Sub-task
>  Components: c client
>Reporter: Michi Mutsuzaki
>Assignee: Michael Han
>  Labels: reconfiguration
> Fix For: 3.5.3, 3.6.0
>
> Attachments: ZOOKEEPER-2152.patch
>
>
> I'm seeing this failure in the c client test once in a while:
> {noformat}
> [exec] 
> /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/trunk/src/c/tests/TestReconfig.cc:474:
>  Assertion: assertion failed [Expression: found != string::npos, 
> 10.10.10.4:2004 not in newComing list]
> {noformat}
> https://builds.apache.org/job/ZooKeeper-trunk/2640/console



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: RC1 issues (was: Re: [VOTE] Apache ZooKeeper release 3.5.2-alpha candidate 1)

[Flavio Junqueira]

> On 03 Jul 2016, at 17:53, Chris Nauroth  wrote:
> 
> For my part, I got a successful full test run from RC1 before starting the
> [VOTE].  The problem with the silent failure of multi tests could have
> snuck past me easily though.  (Flavio, thank you for filing
> ZOOKEEPER-2463.)  I'm curious to hear test results from others who are
> trying RC1.

The test failures seem to be related to test timing, not bugs, but I haven't 
been able to confirm for the last two I mentioned. Granted that timing is in 
some sense a bug, all I'm saying is that it doesn't seem to indicate a 
regression or anything.

> 
> It looks like we also need an issue to track updating the copyright notice
> in the docs.  I don't believe this is an ASF compliance problem in the
> same way that an erroneous NOTICE file would be, so I propose that we
> address it in 3.5.3.

Agreed, we need an issue for that.

> 
> Flavio, you suggested filing a blocker for the ZooKeeperQuorumServer.cc
> failure.  Did you want that targeted to 3.5.2 or 3.5.3?
> 

I'm suggesting as a blocker for 3.5.3, I think we should proceed with 3.5.2 as 
is and give some love to the C client in the next release.

> Overall, how are people feeling about the RC1 [VOTE] at this point?  Is
> anyone considering a -1, or shall we proceed (keeping in mind it's an
> alpha) with the intent of fixing things in a more rapid 3.5.3 release
> cycle?

I'd say we proceed.

-Flavio

> 
> 
> 
> On 7/3/16, 8:43 AM, "Flavio Junqueira"  wrote:
> 
>> The issue with the TestReconfigServer test is that the client port is
>> still used and we get a bind exception, which prevents the server from
>> starting. To verify this locally, I simply added some code to retry and
>> it works fine with that fix. Going forward we need a better fox.
>> 
>> I haven't able to figure out yet the issue with the
>> Zookeeper_simpleSystem tests.
>> 
>> I have also found something strange with the multi tests. I have created
>> ZK-2463 for this problem and made it a blocker for 3.5.3.
>> 
>> -Flavio
>> 
>>> On 03 Jul 2016, at 15:25, Flavio Junqueira  wrote:
>>> 
>>> I have spun a new ubuntu VM to check the C failures. I get three
>>> failures with the new installation:
>>> 
>>> Zookeeper_simpleSystem::testFirstServerDown : assertion : elapsed 10911
>>> tests/TestClient.cc:411: Assertion: equality assertion failed
>>> [Expected: -101, Actual  : -4]
>>> tests/TestClient.cc:322: Assertion: assertion failed [Expression:
>>> ctx.waitForConnected(zk)]
>>> Failures !!!
>>> Run: 43   Failure total: 2   Failures: 2   Errors: 0
>>> 
>>> 
>>> 
>>> TestReconfigServer::testRemoveFollower/usr/bin/java
>>> ZooKeeper JMX enabled by default
>>> Using config: ./../../build/test/test-cppunit/conf/0.conf
>>> Starting zookeeper ... FAILED TO START
>>> zktest-mt: tests/ZooKeeperQuorumServer.cc:61: void
>>> ZooKeeperQuorumServer::start(): Assertion `system(command.c_str()) == 0'
>>> failed.
>>> /bin/bash: line 5: 47059 Aborted (core dumped)
>>> ZKROOT=./../.. CLASSPATH=$CLASSPATH:$CLOVER_HOME/lib/clover.jar
>>> ${dir}$tst
>>> 
>>> -Flavio
>>> 
>>> 
 On 03 Jul 2016, at 15:19, Edward Ribeiro 
 wrote:
 
 Hi Flavio,
 
 
 On Sun, Jul 3, 2016 at 5:54 AM, Flavio Junqueira >>> > wrote:
 Hey Eddie,
 
 A few comments on your points:
 
> 
> - the copyright notice is still dating "2008-2013". It's worth
> updating to
> the current year?
 
 Where are you seeing this? The NOTICE file is correct from what I can
 see.
 
 ​Ops, sorry. I was referring to the PDFs and HTMLs in the docs/
 folder. Even after running "ant docs" the footnote has "2008-2013"
 copyright. Images attached.
 
 
 
> - I consistently ran on an test error equals to the one at
> https://builds.apache.org/job/ZooKeeper-trunk/2982/console
> 
>  >
 
 I think this is ZK-2152, which Chris has moved to 3.5.3, so even
 though it isn't ideal. it is expected.
 
 ​Got it. :)
 ​ 
 
> - Also this one:
> 
> https://mail-archives.apache.org/mod_mbox/zookeeper-dev/201601.mbox/%3C
> 1279938263.1283.1453526737790.JavaMail.jenkins@crius%3E
>  C1279938263.1283.1453526737790.JavaMail.jenkins@crius%3E>
> 
 
 I don't know if there is a jira for this one. If not, better create
 one and make it a blocker.
 
 ​Okay, gonna look for and do this.
 
 
> - In fact, there were 14 failing tests total (I suspect all of them
> related
> to the C tests). Any ideas? A couple of flacky tests?
> 
> 
 
 In general, having a release with so many tests failing is bad. I
 didn't get these test failures, s

ZooKeeper_branch35_solaris - Build # 159 - Still Failing

[Apache Jenkins Server]

See https://builds.apache.org/job/ZooKeeper_branch35_solaris/159/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 418110 lines...]
[junit] 2016-07-03 17:20:54,200 [myid:] - INFO  [main:JMXEnv@146] - 
ensureOnly:[]
[junit] 2016-07-03 17:20:54,201 [myid:] - INFO  [main:ClientBase@466] - 
STARTING server
[junit] 2016-07-03 17:20:54,201 [myid:] - INFO  [main:ClientBase@386] - 
CREATING server instance 127.0.0.1:11222
[junit] 2016-07-03 17:20:54,202 [myid:] - INFO  
[main:NIOServerCnxnFactory@673] - Configuring NIO connection handler with 10s 
sessionless connection timeout, 2 selector thread(s), 16 worker threads, and 64 
kB direct buffers.
[junit] 2016-07-03 17:20:54,202 [myid:] - INFO  
[main:NIOServerCnxnFactory@686] - binding to port 0.0.0.0/0.0.0.0:11222
[junit] 2016-07-03 17:20:54,203 [myid:] - INFO  [main:ClientBase@361] - 
STARTING server instance 127.0.0.1:11222
[junit] 2016-07-03 17:20:54,203 [myid:] - INFO  [main:ZooKeeperServer@858] 
- minSessionTimeout set to 6000
[junit] 2016-07-03 17:20:54,204 [myid:] - INFO  [main:ZooKeeperServer@867] 
- maxSessionTimeout set to 6
[junit] 2016-07-03 17:20:54,204 [myid:] - INFO  [main:ZooKeeperServer@156] 
- Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 
6 datadir 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch35_solaris/branch-3.5/build/test/tmp/test1630865093280186957.junit.dir/version-2
 snapdir 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch35_solaris/branch-3.5/build/test/tmp/test1630865093280186957.junit.dir/version-2
[junit] 2016-07-03 17:20:54,204 [myid:] - INFO  [main:FileSnap@83] - 
Reading snapshot 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch35_solaris/branch-3.5/build/test/tmp/test1630865093280186957.junit.dir/version-2/snapshot.b
[junit] 2016-07-03 17:20:54,206 [myid:] - INFO  [main:FileTxnSnapLog@298] - 
Snapshotting: 0xb to 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch35_solaris/branch-3.5/build/test/tmp/test1630865093280186957.junit.dir/version-2/snapshot.b
[junit] 2016-07-03 17:20:54,208 [myid:] - INFO  
[main:FourLetterWordMain@85] - connecting to 127.0.0.1 11222
[junit] 2016-07-03 17:20:54,208 [myid:] - INFO  
[NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11222:NIOServerCnxnFactory$AcceptThread@296]
 - Accepted socket connection from /127.0.0.1:34316
[junit] 2016-07-03 17:20:54,209 [myid:] - INFO  
[NIOWorkerThread-1:NIOServerCnxn@485] - Processing stat command from 
/127.0.0.1:34316
[junit] 2016-07-03 17:20:54,209 [myid:] - INFO  
[NIOWorkerThread-1:StatCommand@49] - Stat command output
[junit] 2016-07-03 17:20:54,210 [myid:] - INFO  
[NIOWorkerThread-1:NIOServerCnxn@607] - Closed socket connection for client 
/127.0.0.1:34316 (no session established for client)
[junit] 2016-07-03 17:20:54,210 [myid:] - INFO  [main:JMXEnv@228] - 
ensureParent:[InMemoryDataTree, StandaloneServer_port]
[junit] 2016-07-03 17:20:54,211 [myid:] - INFO  [main:JMXEnv@245] - 
expect:InMemoryDataTree
[junit] 2016-07-03 17:20:54,212 [myid:] - INFO  [main:JMXEnv@249] - 
found:InMemoryDataTree 
org.apache.ZooKeeperService:name0=StandaloneServer_port11222,name1=InMemoryDataTree
[junit] 2016-07-03 17:20:54,212 [myid:] - INFO  [main:JMXEnv@245] - 
expect:StandaloneServer_port
[junit] 2016-07-03 17:20:54,212 [myid:] - INFO  [main:JMXEnv@249] - 
found:StandaloneServer_port 
org.apache.ZooKeeperService:name0=StandaloneServer_port11222
[junit] 2016-07-03 17:20:54,212 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@82] - Memory used 17641
[junit] 2016-07-03 17:20:54,212 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@87] - Number of threads 24
[junit] 2016-07-03 17:20:54,212 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@102] - FINISHED TEST METHOD 
testQuota
[junit] 2016-07-03 17:20:54,213 [myid:] - INFO  [main:ClientBase@543] - 
tearDown starting
[junit] 2016-07-03 17:20:54,292 [myid:] - INFO  [main:ZooKeeper@1313] - 
Session: 0x1222ec375ae closed
[junit] 2016-07-03 17:20:54,292 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@513] - EventThread shut down for 
session: 0x1222ec375ae
[junit] 2016-07-03 17:20:54,292 [myid:] - INFO  [main:ClientBase@513] - 
STOPPING server
[junit] 2016-07-03 17:20:54,293 [myid:] - INFO  
[NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11222:NIOServerCnxnFactory$AcceptThread@219]
 - accept thread exitted run method
[junit] 2016-07-03 17:20:54,293 [myid:] - INFO  
[ConnnectionExpirer:NIOServerCnxnFactory$ConnectionExpirerThread@583] - 
ConnnectionExpirerThread interrupted
[junit] 2016-07-03 17:20:54,293 [myid:] - INFO  
[NIOServerCxnFactory.SelectorThread-0:NIO

Re: RC1 issues (was: Re: [VOTE] Apache ZooKeeper release 3.5.2-alpha candidate 1)

[Chris Nauroth]

For my part, I got a successful full test run from RC1 before starting the
[VOTE].  The problem with the silent failure of multi tests could have
snuck past me easily though.  (Flavio, thank you for filing
ZOOKEEPER-2463.)  I'm curious to hear test results from others who are
trying RC1.

It looks like we also need an issue to track updating the copyright notice
in the docs.  I don't believe this is an ASF compliance problem in the
same way that an erroneous NOTICE file would be, so I propose that we
address it in 3.5.3.

Flavio, you suggested filing a blocker for the ZooKeeperQuorumServer.cc
failure.  Did you want that targeted to 3.5.2 or 3.5.3?

Overall, how are people feeling about the RC1 [VOTE] at this point?  Is
anyone considering a -1, or shall we proceed (keeping in mind it's an
alpha) with the intent of fixing things in a more rapid 3.5.3 release
cycle?

--Chris Nauroth




On 7/3/16, 8:43 AM, "Flavio Junqueira"  wrote:

>The issue with the TestReconfigServer test is that the client port is
>still used and we get a bind exception, which prevents the server from
>starting. To verify this locally, I simply added some code to retry and
>it works fine with that fix. Going forward we need a better fox.
>
>I haven't able to figure out yet the issue with the
>Zookeeper_simpleSystem tests.
>
>I have also found something strange with the multi tests. I have created
>ZK-2463 for this problem and made it a blocker for 3.5.3.
>
>-Flavio
>
>> On 03 Jul 2016, at 15:25, Flavio Junqueira  wrote:
>> 
>> I have spun a new ubuntu VM to check the C failures. I get three
>>failures with the new installation:
>> 
>> Zookeeper_simpleSystem::testFirstServerDown : assertion : elapsed 10911
>> tests/TestClient.cc:411: Assertion: equality assertion failed
>>[Expected: -101, Actual  : -4]
>> tests/TestClient.cc:322: Assertion: assertion failed [Expression:
>>ctx.waitForConnected(zk)]
>> Failures !!!
>> Run: 43   Failure total: 2   Failures: 2   Errors: 0
>> 
>> 
>> 
>> TestReconfigServer::testRemoveFollower/usr/bin/java
>> ZooKeeper JMX enabled by default
>> Using config: ./../../build/test/test-cppunit/conf/0.conf
>> Starting zookeeper ... FAILED TO START
>> zktest-mt: tests/ZooKeeperQuorumServer.cc:61: void
>>ZooKeeperQuorumServer::start(): Assertion `system(command.c_str()) == 0'
>>failed.
>> /bin/bash: line 5: 47059 Aborted (core dumped)
>>ZKROOT=./../.. CLASSPATH=$CLASSPATH:$CLOVER_HOME/lib/clover.jar
>>${dir}$tst
>> 
>> -Flavio
>> 
>> 
>>> On 03 Jul 2016, at 15:19, Edward Ribeiro 
>>>wrote:
>>> 
>>> Hi Flavio,
>>> 
>>> 
>>> On Sun, Jul 3, 2016 at 5:54 AM, Flavio Junqueira >>> wrote:
>>> Hey Eddie,
>>> 
>>> A few comments on your points:
>>> 
 
 - the copyright notice is still dating "2008-2013". It's worth
updating to
 the current year?
>>> 
>>> Where are you seeing this? The NOTICE file is correct from what I can
>>>see.
>>> 
>>> ​Ops, sorry. I was referring to the PDFs and HTMLs in the docs/
>>>folder. Even after running "ant docs" the footnote has "2008-2013"
>>>copyright. Images attached.
>>> 
>>> 
>>> 
 - I consistently ran on an test error equals to the one at
 https://builds.apache.org/job/ZooKeeper-trunk/2982/console

>
>>> 
>>> I think this is ZK-2152, which Chris has moved to 3.5.3, so even
>>>though it isn't ideal. it is expected.
>>> 
>>> ​Got it. :)
>>> ​ 
>>> 
 - Also this one:
 
https://mail-archives.apache.org/mod_mbox/zookeeper-dev/201601.mbox/%3C
1279938263.1283.1453526737790.JavaMail.jenkins@crius%3E

 
>>> 
>>> I don't know if there is a jira for this one. If not, better create
>>>one and make it a blocker.
>>> 
>>> ​Okay, gonna look for and do this.
>>> 
>>> 
 - In fact, there were 14 failing tests total (I suspect all of them
related
 to the C tests). Any ideas? A couple of flacky tests?
 
 
>>> 
>>> In general, having a release with so many tests failing is bad. I
>>>didn't get these test failures, so it would be great to report them or
>>>make sure that there are jiras for it.
>>> 
>>> ​Right. I was only skep​tical of my own tests because I ran the unit
>>>tests on a relatively old Ubuntu version, even though it was Java 1.7.
>>>So, I am running the tests on a newer Linux soon just to make sure it
>>>was not a false negative.
>>> 
>>> 
>>> 
>>> Test failures are possibly an indication that something is bad with
>>>the RC, so I wouldn't have +1 it if I had observed all those. It might
>>>be ok given that this is still labeled alpha.
>>> 
>>> ​Excuse me. I only +1'ed because I suspect the errors are restricted
>>>to the C binding and my Ubuntu version, etc. But I should h

Re: RC1 issues (was: Re: [VOTE] Apache ZooKeeper release 3.5.2-alpha candidate 1)

[Flavio Junqueira]

The issue with the TestReconfigServer test is that the client port is still 
used and we get a bind exception, which prevents the server from starting. To 
verify this locally, I simply added some code to retry and it works fine with 
that fix. Going forward we need a better fox.

I haven't able to figure out yet the issue with the Zookeeper_simpleSystem 
tests. 

I have also found something strange with the multi tests. I have created 
ZK-2463 for this problem and made it a blocker for 3.5.3.

-Flavio

> On 03 Jul 2016, at 15:25, Flavio Junqueira  wrote:
> 
> I have spun a new ubuntu VM to check the C failures. I get three failures 
> with the new installation:
> 
> Zookeeper_simpleSystem::testFirstServerDown : assertion : elapsed 10911
> tests/TestClient.cc:411: Assertion: equality assertion failed [Expected: 
> -101, Actual  : -4]
> tests/TestClient.cc:322: Assertion: assertion failed [Expression: 
> ctx.waitForConnected(zk)]
> Failures !!!
> Run: 43   Failure total: 2   Failures: 2   Errors: 0
> 
> 
> 
> TestReconfigServer::testRemoveFollower/usr/bin/java
> ZooKeeper JMX enabled by default
> Using config: ./../../build/test/test-cppunit/conf/0.conf
> Starting zookeeper ... FAILED TO START
> zktest-mt: tests/ZooKeeperQuorumServer.cc:61: void 
> ZooKeeperQuorumServer::start(): Assertion `system(command.c_str()) == 0' 
> failed.
> /bin/bash: line 5: 47059 Aborted (core dumped) ZKROOT=./../.. 
> CLASSPATH=$CLASSPATH:$CLOVER_HOME/lib/clover.jar ${dir}$tst
> 
> -Flavio
> 
> 
>> On 03 Jul 2016, at 15:19, Edward Ribeiro  wrote:
>> 
>> Hi Flavio,
>> 
>> 
>> On Sun, Jul 3, 2016 at 5:54 AM, Flavio Junqueira > > wrote:
>> Hey Eddie,
>> 
>> A few comments on your points:
>> 
>>> 
>>> - the copyright notice is still dating "2008-2013". It's worth updating to
>>> the current year?
>> 
>> Where are you seeing this? The NOTICE file is correct from what I can see.
>> 
>> ​Ops, sorry. I was referring to the PDFs and HTMLs in the docs/ folder. Even 
>> after running "ant docs" the footnote has "2008-2013" copyright. Images 
>> attached.
>> 
>> 
>> 
>>> - I consistently ran on an test error equals to the one at
>>> https://builds.apache.org/job/ZooKeeper-trunk/2982/console 
>>>  
>>> >> >
>> 
>> I think this is ZK-2152, which Chris has moved to 3.5.3, so even though it 
>> isn't ideal. it is expected.
>> 
>> ​Got it. :)
>> ​ 
>> 
>>> - Also this one:
>>> https://mail-archives.apache.org/mod_mbox/zookeeper-dev/201601.mbox/%3C1279938263.1283.1453526737790.JavaMail.jenkins@crius%3E
>>>  
>>> 
>>> 
>> 
>> I don't know if there is a jira for this one. If not, better create one and 
>> make it a blocker.
>> 
>> ​Okay, gonna look for and do this.
>> 
>> 
>>> - In fact, there were 14 failing tests total (I suspect all of them related
>>> to the C tests). Any ideas? A couple of flacky tests?
>>> 
>>> 
>> 
>> In general, having a release with so many tests failing is bad. I didn't get 
>> these test failures, so it would be great to report them or make sure that 
>> there are jiras for it.
>> 
>> ​Right. I was only skep​tical of my own tests because I ran the unit tests 
>> on a relatively old Ubuntu version, even though it was Java 1.7. So, I am 
>> running the tests on a newer Linux soon just to make sure it was not a false 
>> negative.
>> 
>> 
>> 
>> Test failures are possibly an indication that something is bad with the RC, 
>> so I wouldn't have +1 it if I had observed all those. It might be ok given 
>> that this is still labeled alpha.
>> 
>> ​Excuse me. I only +1'ed because I suspect the errors are restricted to the 
>> C binding and my Ubuntu version, etc. But I should have researched further 
>> before giving +1, nevertheless. Point taken. :) 
>> 
>> Edward
> 

[jira] [Created] (ZOOKEEPER-2463) TestMulti is broken in the C client

[Flavio Junqueira (JIRA)]

Flavio Junqueira created ZOOKEEPER-2463:
---

 Summary: TestMulti is broken in the C client
 Key: ZOOKEEPER-2463
 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2463
 Project: ZooKeeper
  Issue Type: Bug
Reporter: Flavio Junqueira
Priority: Blocker
 Fix For: 3.5.3, 3.6.0


I noticed that all multi tests seem to be timing out and they are failing 
silently. This is the output that I'm observing:

{noformat}
Zookeeper_multi::testCreate : assertion : elapsed 10001
Zookeeper_multi::testCreateDelete : assertion : elapsed 10001
Zookeeper_multi::testInvalidVersion : assertion : elapsed 10001
Zookeeper_multi::testNestedCreate : assertion : elapsed 10001
Zookeeper_multi::testSetData : assertion : elapsed 10001
Zookeeper_multi::testUpdateConflict : assertion : elapsed 10001
Zookeeper_multi::testDeleteUpdateConflict : assertion : elapsed 10001
Zookeeper_multi::testAsyncMulti : assertion : elapsed 10001
Zookeeper_multi::testMultiFail : assertion : elapsed 10001
Zookeeper_multi::testCheck : assertion : elapsed 10001
Zookeeper_multi::testWatch : assertion : elapsed 10001
Zookeeper_multi::testSequentialNodeCreateInAsyncMulti : assertion : elapsed 
10001
{noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

ZooKeeper_branch34_openjdk7 - Build # 1126 - Still Failing

[Apache Jenkins Server]

See https://builds.apache.org/job/ZooKeeper_branch34_openjdk7/1126/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 217464 lines...]
[junit] 2016-07-03 15:20:46,256 [myid:] - INFO  [main:JMXEnv@246] - 
expect:StandaloneServer_port
[junit] 2016-07-03 15:20:46,256 [myid:] - INFO  [main:JMXEnv@250] - 
found:StandaloneServer_port 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221
[junit] 2016-07-03 15:20:46,257 [myid:] - INFO  [main:ClientBase@490] - 
STOPPING server
[junit] 2016-07-03 15:20:46,257 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@219] - 
NIOServerCnxn factory exited run method
[junit] 2016-07-03 15:20:46,257 [myid:] - INFO  [main:ZooKeeperServer@469] 
- shutting down
[junit] 2016-07-03 15:20:46,257 [myid:] - INFO  
[main:SessionTrackerImpl@225] - Shutting down
[junit] 2016-07-03 15:20:46,258 [myid:] - INFO  
[main:PrepRequestProcessor@765] - Shutting down
[junit] 2016-07-03 15:20:46,258 [myid:] - INFO  
[main:SyncRequestProcessor@209] - Shutting down
[junit] 2016-07-03 15:20:46,258 [myid:] - INFO  [ProcessThread(sid:0 
cport:11221)::PrepRequestProcessor@143] - PrepRequestProcessor exited loop!
[junit] 2016-07-03 15:20:46,258 [myid:] - INFO  
[SyncThread:0:SyncRequestProcessor@187] - SyncRequestProcessor exited!
[junit] 2016-07-03 15:20:46,259 [myid:] - INFO  
[main:FinalRequestProcessor@402] - shutdown of request processor complete
[junit] 2016-07-03 15:20:46,259 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2016-07-03 15:20:46,260 [myid:] - INFO  [main:JMXEnv@146] - 
ensureOnly:[]
[junit] 2016-07-03 15:20:46,262 [myid:] - INFO  [main:ClientBase@443] - 
STARTING server
[junit] 2016-07-03 15:20:46,262 [myid:] - INFO  [main:ClientBase@364] - 
CREATING server instance 127.0.0.1:11221
[junit] 2016-07-03 15:20:46,262 [myid:] - INFO  
[main:NIOServerCnxnFactory@89] - binding to port 0.0.0.0/0.0.0.0:11221
[junit] 2016-07-03 15:20:46,263 [myid:] - INFO  [main:ClientBase@339] - 
STARTING server instance 127.0.0.1:11221
[junit] 2016-07-03 15:20:46,263 [myid:] - INFO  [main:ZooKeeperServer@170] 
- Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 
6 datadir 
/x1/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_openjdk7/branch-3.4/build/test/tmp/test2755257542288713535.junit.dir/version-2
 snapdir 
/x1/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_openjdk7/branch-3.4/build/test/tmp/test2755257542288713535.junit.dir/version-2
[junit] 2016-07-03 15:20:46,268 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2016-07-03 15:20:46,269 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@192] - 
Accepted socket connection from /127.0.0.1:37413
[junit] 2016-07-03 15:20:46,269 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxn@827] - Processing 
stat command from /127.0.0.1:37413
[junit] 2016-07-03 15:20:46,269 [myid:] - INFO  
[Thread-4:NIOServerCnxn$StatCommand@663] - Stat command output
[junit] 2016-07-03 15:20:46,270 [myid:] - INFO  
[Thread-4:NIOServerCnxn@1008] - Closed socket connection for client 
/127.0.0.1:37413 (no session established for client)
[junit] 2016-07-03 15:20:46,270 [myid:] - INFO  [main:JMXEnv@229] - 
ensureParent:[InMemoryDataTree, StandaloneServer_port]
[junit] 2016-07-03 15:20:46,272 [myid:] - INFO  [main:JMXEnv@246] - 
expect:InMemoryDataTree
[junit] 2016-07-03 15:20:46,273 [myid:] - INFO  [main:JMXEnv@250] - 
found:InMemoryDataTree 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221,name1=InMemoryDataTree
[junit] 2016-07-03 15:20:46,273 [myid:] - INFO  [main:JMXEnv@246] - 
expect:StandaloneServer_port
[junit] 2016-07-03 15:20:46,273 [myid:] - INFO  [main:JMXEnv@250] - 
found:StandaloneServer_port 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221
[junit] 2016-07-03 15:20:46,274 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@58] - Memory used 26415
[junit] 2016-07-03 15:20:46,274 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@63] - Number of threads 20
[junit] 2016-07-03 15:20:46,274 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@78] - FINISHED TEST METHOD testQuota
[junit] 2016-07-03 15:20:46,274 [myid:] - INFO  [main:ClientBase@520] - 
tearDown starting
[junit] 2016-07-03 15:20:46,339 [myid:] - INFO  [main:ZooKeeper@684] - 
Session: 0x155b158f854 closed
[junit] 2016-07-03 15:20:46,339 [myid:] - INFO  [main:ClientBase@490] - 
STOPPING server
[junit] 2016-07-03 15:20:46,339 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@519] - EventThread shut down for 
session: 0x155b158f854
[junit] 2016-07-03 15:20:46,340 [myid:] - INFO  
[N

Re: RC1 issues (was: Re: [VOTE] Apache ZooKeeper release 3.5.2-alpha candidate 1)

[Flavio Junqueira]

I have spun a new ubuntu VM to check the C failures. I get three failures with 
the new installation:

Zookeeper_simpleSystem::testFirstServerDown : assertion : elapsed 10911
tests/TestClient.cc:411: Assertion: equality assertion failed [Expected: -101, 
Actual  : -4]
tests/TestClient.cc:322: Assertion: assertion failed [Expression: 
ctx.waitForConnected(zk)]
Failures !!!
Run: 43   Failure total: 2   Failures: 2   Errors: 0



TestReconfigServer::testRemoveFollower/usr/bin/java
ZooKeeper JMX enabled by default
Using config: ./../../build/test/test-cppunit/conf/0.conf
Starting zookeeper ... FAILED TO START
zktest-mt: tests/ZooKeeperQuorumServer.cc:61: void 
ZooKeeperQuorumServer::start(): Assertion `system(command.c_str()) == 0' failed.
/bin/bash: line 5: 47059 Aborted (core dumped) ZKROOT=./../.. 
CLASSPATH=$CLASSPATH:$CLOVER_HOME/lib/clover.jar ${dir}$tst

-Flavio


> On 03 Jul 2016, at 15:19, Edward Ribeiro  wrote:
> 
> Hi Flavio,
> 
> 
> On Sun, Jul 3, 2016 at 5:54 AM, Flavio Junqueira  > wrote:
> Hey Eddie,
> 
> A few comments on your points:
> 
> >
> > - the copyright notice is still dating "2008-2013". It's worth updating to
> > the current year?
> 
> Where are you seeing this? The NOTICE file is correct from what I can see.
> 
> ​Ops, sorry. I was referring to the PDFs and HTMLs in the docs/ folder. Even 
> after running "ant docs" the footnote has "2008-2013" copyright. Images 
> attached.
> 
>  
> 
> > - I consistently ran on an test error equals to the one at
> > https://builds.apache.org/job/ZooKeeper-trunk/2982/console 
> >  
> >  > >
> 
> I think this is ZK-2152, which Chris has moved to 3.5.3, so even though it 
> isn't ideal. it is expected.
> 
> ​Got it. :)
> ​ 
> 
> > - Also this one:
> > https://mail-archives.apache.org/mod_mbox/zookeeper-dev/201601.mbox/%3C1279938263.1283.1453526737790.JavaMail.jenkins@crius%3E
> >  
> > 
> >
> 
> I don't know if there is a jira for this one. If not, better create one and 
> make it a blocker.
> 
> ​Okay, gonna look for and do this.
>  
> 
> > - In fact, there were 14 failing tests total (I suspect all of them related
> > to the C tests). Any ideas? A couple of flacky tests?
> >
> >
> 
> In general, having a release with so many tests failing is bad. I didn't get 
> these test failures, so it would be great to report them or make sure that 
> there are jiras for it.
> 
> ​Right. I was only skep​tical of my own tests because I ran the unit tests on 
> a relatively old Ubuntu version, even though it was Java 1.7. So, I am 
> running the tests on a newer Linux soon just to make sure it was not a false 
> negative.
> 
>  
> 
> Test failures are possibly an indication that something is bad with the RC, 
> so I wouldn't have +1 it if I had observed all those. It might be ok given 
> that this is still labeled alpha.
> 
> ​Excuse me. I only +1'ed because I suspect the errors are restricted to the C 
> binding and my Ubuntu version, etc. But I should have researched further 
> before giving +1, nevertheless. Point taken. :) 
> 
> Edward

Re: RC1 issues (was: Re: [VOTE] Apache ZooKeeper release 3.5.2-alpha candidate 1)

[Edward Ribeiro]

Hi Flavio,


On Sun, Jul 3, 2016 at 5:54 AM, Flavio Junqueira  wrote:

> Hey Eddie,
>
> A few comments on your points:
>
> >
> > - the copyright notice is still dating "2008-2013". It's worth updating
> to
> > the current year?
>
> Where are you seeing this? The NOTICE file is correct from what I can see.
>

​Ops, sorry. I was referring to the PDFs and HTMLs in the docs/ folder.
Even after running "ant docs" the footnote has "2008-2013" copyright.
Images attached.



>
> > - I consistently ran on an test error equals to the one at
> > https://builds.apache.org/job/ZooKeeper-trunk/2982/console <
> https://builds.apache.org/job/ZooKeeper-trunk/2982/console>
>
> I think this is ZK-2152, which Chris has moved to 3.5.3, so even though it
> isn't ideal. it is expected.
>

​Got it. :)
​


>
> > - Also this one:
> >
> https://mail-archives.apache.org/mod_mbox/zookeeper-dev/201601.mbox/%3C1279938263.1283.1453526737790.JavaMail.jenkins@crius%3E
> >
>
> I don't know if there is a jira for this one. If not, better create one
> and make it a blocker.
>

​Okay, gonna look for and do this.


>
> > - In fact, there were 14 failing tests total (I suspect all of them
> related
> > to the C tests). Any ideas? A couple of flacky tests?
> >
> >
>
> In general, having a release with so many tests failing is bad. I didn't
> get these test failures, so it would be great to report them or make sure
> that there are jiras for it.
>

​Right. I was only skep​tical of my own tests because I ran the unit tests
on a relatively old Ubuntu version, even though it was Java 1.7. So, I am
running the tests on a newer Linux soon just to make sure it was not a
false negative.



>
> Test failures are possibly an indication that something is bad with the
> RC, so I wouldn't have +1 it if I had observed all those. It might be ok
> given that this is still labeled alpha.
>

​Excuse me. I only +1'ed because I suspect the errors are restricted to the
C binding and my Ubuntu version, etc. But I should have researched further
before giving +1, nevertheless. Point taken. :)

Edward

ZooKeeper_branch35_openjdk7 - Build # 140 - Still Failing

[Apache Jenkins Server]

See https://builds.apache.org/job/ZooKeeper_branch35_openjdk7/140/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 435909 lines...]
 [exec] Log Message Received: [2016-07-03 
10:10:53,139:1328(0x2ae978828540):ZOO_INFO@testLogCallbackInit@993: 
testLogCallbackInit #8]
 [exec] Log Message Received: [2016-07-03 
10:10:53,139:1328(0x2ae978828540):ZOO_INFO@testLogCallbackInit@993: 
testLogCallbackInit #9]
 [exec] Log Message Received: [2016-07-03 
10:10:53,139:1328(0x2ae978828540):ZOO_INFO@zookeeper_close@3257: Closing 
zookeeper sessionId=0x1026867bab2000e to [127.0.0.1:22181]
 [exec] ]
 [exec]  : elapsed 1001 : OK
 [exec] Zookeeper_simpleSystem::testLogCallbackClearLog Message Received: 
[2016-07-03 10:10:53,140:1328(0x2ae978828540):ZOO_INFO@log_env@1027: Client 
environment:zookeeper.version=zookeeper C client 3.5.2]
 [exec] Log Message Received: [2016-07-03 
10:10:53,140:1328(0x2ae978828540):ZOO_INFO@log_env@1031: Client 
environment:host.name=jenkins-ubuntu1]
 [exec] Log Message Received: [2016-07-03 
10:10:53,140:1328(0x2ae978828540):ZOO_INFO@log_env@1038: Client 
environment:os.name=Linux]
 [exec] Log Message Received: [2016-07-03 
10:10:53,140:1328(0x2ae978828540):ZOO_INFO@log_env@1039: Client 
environment:os.arch=3.19.0-25-generic]
 [exec] Log Message Received: [2016-07-03 
10:10:53,140:1328(0x2ae978828540):ZOO_INFO@log_env@1040: Client 
environment:os.version=#26~14.04.1-Ubuntu SMP Fri Jul 24 21:16:20 UTC 2015]
 [exec] Log Message Received: [2016-07-03 
10:10:53,140:1328(0x2ae978828540):ZOO_INFO@log_env@1048: Client 
environment:user.name=jenkins]
 [exec] Log Message Received: [2016-07-03 
10:10:53,140:1328(0x2ae978828540):ZOO_INFO@log_env@1056: Client 
environment:user.home=/home/jenkins]
 [exec] Log Message Received: [2016-07-03 
10:10:53,140:1328(0x2ae978828540):ZOO_INFO@log_env@1068: Client 
environment:user.dir=/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch35_openjdk7/branch-3.5/build/test/test-cppunit]
 [exec] Log Message Received: [2016-07-03 
10:10:53,140:1328(0x2ae978828540):ZOO_INFO@zookeeper_init_internal@: 
Initiating client connection, host=127.0.0.1:22181 sessionTimeout=1 
watcher=0x45d2a0 sessionId=0 sessionPasswd= context=0x7ffe7b3ba4a0 
flags=0]
 [exec] Log Message Received: [2016-07-03 
10:10:53,142:1328(0x2ae97a885700):ZOO_INFO@check_events@2357: initiated 
connection to server [127.0.0.1:22181]]
 [exec] Log Message Received: [2016-07-03 
10:10:53,149:1328(0x2ae97a885700):ZOO_INFO@check_events@2409: session 
establishment complete on server [127.0.0.1:22181], 
sessionId=0x1026867bab2000f, negotiated timeout=1 ]
 [exec]  : elapsed 1001 : OK
 [exec] Zookeeper_simpleSystem::testAsyncWatcherAutoReset ZooKeeper server 
started : elapsed 10538 : OK
 [exec] Zookeeper_simpleSystem::testDeserializeString : elapsed 0 : OK
 [exec] Zookeeper_simpleSystem::testFirstServerDown : elapsed 1003 : OK
 [exec] Zookeeper_simpleSystem::testNullData : elapsed 1042 : OK
 [exec] Zookeeper_simpleSystem::testIPV6 : elapsed 1007 : OK
 [exec] Zookeeper_simpleSystem::testCreate : elapsed 1014 : OK
 [exec] Zookeeper_simpleSystem::testPath : elapsed 1026 : OK
 [exec] Zookeeper_simpleSystem::testPathValidation : elapsed 1083 : OK
 [exec] Zookeeper_simpleSystem::testPing : elapsed 17370 : OK
 [exec] Zookeeper_simpleSystem::testAcl : elapsed 1022 : OK
 [exec] Zookeeper_simpleSystem::testChroot : elapsed 3074 : OK
 [exec] Zookeeper_simpleSystem::testAuth ZooKeeper server started ZooKeeper 
server started : elapsed 32420 : OK
 [exec] Zookeeper_simpleSystem::testHangingClient : elapsed 1046 : OK
 [exec] Zookeeper_simpleSystem::testWatcherAutoResetWithGlobal ZooKeeper 
server started ZooKeeper server started ZooKeeper server started : elapsed 
16966 : OK
 [exec] Zookeeper_simpleSystem::testWatcherAutoResetWithLocal ZooKeeper 
server started ZooKeeper server started ZooKeeper server started : elapsed 
17444 : OK
 [exec] Zookeeper_simpleSystem::testGetChildren2 : elapsed 1054 : OK
 [exec] Zookeeper_simpleSystem::testLastZxid : elapsed 4523 : OK
 [exec] Zookeeper_simpleSystem::testRemoveWatchers ZooKeeper server started 
: elapsed 5488 : OK
 [exec] Zookeeper_readOnly::testReadOnly : elapsed 4237 : OK
 [exec] 
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch35_openjdk7/branch-3.5/src/c/tests/TestReconfig.cc:183:
 Assertion: equality assertion failed [Expected: 1, Actual  : 0]
 [exec] Failures !!!
 [exec] Run: 72   Failure total: 1   Failures: 1   Errors: 0
 [exec] FAIL: zktest-mt
 [exec] ==
 [exec] 1 of 2 tests failed
 [exec] Please report to u...@zookeeper.apache.org
 [exec] ==
 [exec] make[1]: Leaving directo

RC1 issues (was: Re: [VOTE] Apache ZooKeeper release 3.5.2-alpha candidate 1)

[Flavio Junqueira]

Hey Eddie,

A few comments on your points:

> On 02 Jul 2016, at 23:54, Edward Ribeiro  wrote:
> 
> +1 (non-binding)
> 
> - built ZK from source
> - ran all the unit tests
> - generated and checked javadocs
> - generated and checked docs
> - executed few manual test (zkCli.sh) and 4lw
> 
> Some small issues (imho):
> 
> - the copyright notice is still dating "2008-2013". It's worth updating to
> the current year?

Where are you seeing this? The NOTICE file is correct from what I can see.

> - I consistently ran on an test error equals to the one at
> https://builds.apache.org/job/ZooKeeper-trunk/2982/console 
> 

I think this is ZK-2152, which Chris has moved to 3.5.3, so even though it 
isn't ideal. it is expected.

> - Also this one:
> https://mail-archives.apache.org/mod_mbox/zookeeper-dev/201601.mbox/%3C1279938263.1283.1453526737790.JavaMail.jenkins@crius%3E
> 

I don't know if there is a jira for this one. If not, better create one and 
make it a blocker.

> - In fact, there were 14 failing tests total (I suspect all of them related
> to the C tests). Any ideas? A couple of flacky tests?
> 
> 

In general, having a release with so many tests failing is bad. I didn't get 
these test failures, so it would be great to report them or make sure that 
there are jiras for it.

Test failures are possibly an indication that something is bad with the RC, so 
I wouldn't have +1 it if I had observed all those. It might be ok given that 
this is still labeled alpha.

-Flavio


> Regards,
> Eddie
> 
> 
> On Sat, Jul 2, 2016 at 1:46 PM, Rakesh Radhakrishnan <
> rakeshr.apa...@gmail.com> wrote:
> 
>> +1
>> 
>> - built zookeeper jar from source,
>> - ran unit test cases, few zkCli commands, few four letter words,
>> - tested few scenarios against Hadoop-2.7.2 version(3 node Kerberos secure
>> cluster environment).
>> 
>> Thanks Chris for making the release.
>> 
>> Regards,
>> Rakesh
>> 
>> On Sat, Jul 2, 2016 at 7:43 PM, Flavio Junqueira  wrote:
>> 
>>> +1
>>> 
>>> - Checked license information
>>> - Ran RAT tool
>>> - Ran tests
>>> - Ran some smoke tests
>>> - Verified digests and signature
>>> - Checked release notes
>>> 
>>> All of the above LGTM
>>> 
>>> -Flavio
>>> 
>>> 
 On 01 Jul 2016, at 08:45, Chris Nauroth 
>>> wrote:
 
 This is a release candidate for 3.5.2-alpha. The full release notes are
 available at:
 
 
>>> 
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310801&v
 ersion=12331981
 
 *** Please download, test and vote by July 5th 2016, 23:59 UTC+0. ***
 
 Source files:
 http://people.apache.org/~cnauroth/zookeeper-3.5.2-alpha-candidate-1/
 
 Maven staging repo:
 
>>> 
>> https://repository.apache.org/content/groups/staging/org/apache/zookeeper/z
 ookeeper/3.5.2-alpha/
 
 The tag to be voted upon:
 https://svn.apache.org/repos/asf/zookeeper/tags/release-3.5.2-rc1/
 
 ZooKeeper's KEYS file containing PGP keys we use to sign the release:
 http://www.apache.org/dist/zookeeper/KEYS
 
 Should we release this candidate?
 
 
 --Chris Nauroth
 
 
 
 
>>> 
>>> 
>> 

[jira] [Commented] (ZOOKEEPER-2152) Intermittent failure in TestReconfig.cc

[Flavio Junqueira (JIRA)]

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15360466#comment-15360466
 ] 

Flavio Junqueira commented on ZOOKEEPER-2152:
-

The fix version for this jira is 3.6.0, should it be marked to be fixed in 3.5 
as well?

> Intermittent failure in TestReconfig.cc
> ---
>
> Key: ZOOKEEPER-2152
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2152
> Project: ZooKeeper
>  Issue Type: Sub-task
>  Components: c client
>Reporter: Michi Mutsuzaki
>Assignee: Michael Han
>  Labels: reconfiguration
> Fix For: 3.6.0
>
> Attachments: ZOOKEEPER-2152.patch
>
>
> I'm seeing this failure in the c client test once in a while:
> {noformat}
> [exec] 
> /home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk/trunk/src/c/tests/TestReconfig.cc:474:
>  Assertion: assertion failed [Expression: found != string::npos, 
> 10.10.10.4:2004 not in newComing list]
> {noformat}
> https://builds.apache.org/job/ZooKeeper-trunk/2640/console



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

ZooKeeper-trunk-solaris - Build # 1218 - Still Failing

[Apache Jenkins Server]

See https://builds.apache.org/job/ZooKeeper-trunk-solaris/1218/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 300 lines...]
[junit] 2016-07-03 07:27:55,938 [myid:] - INFO  [main:Environment@109] - 
Client 
environment:user.dir=/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper-trunk-solaris/trunk/build/test
[junit] 2016-07-03 07:27:55,938 [myid:] - INFO  [main:Environment@109] - 
Client environment:os.memory.free=51MB
[junit] 2016-07-03 07:27:55,938 [myid:] - INFO  [main:Environment@109] - 
Client environment:os.memory.max=454MB
[junit] 2016-07-03 07:27:55,938 [myid:] - INFO  [main:Environment@109] - 
Client environment:os.memory.total=61MB
[junit] 2016-07-03 07:27:56,367 [myid:] - INFO  [main:ZooKeeper@855] - 
Initiating client connection, connectString=127.0.0.1:11222 
sessionTimeout=3 watcher=org.apache.zookeeper.CustomHostProviderTest@13ceeb6
[junit] 2016-07-03 07:27:57,756 [myid:] - INFO  [main:ZooKeeper@855] - 
Initiating client connection, connectString=127.0.0.1:11222 
sessionTimeout=3 watcher=org.apache.zookeeper.CustomHostProviderTest@13ceeb6
[junit] 2016-07-03 07:27:57,758 [myid:] - INFO  [main:PortAssignment@85] - 
Assigned port 11223 from range 11221 - 32767.
[junit] 2016-07-03 07:27:57,758 [myid:] - INFO  
[main:ClientCnxnSocketNIO@378] - testableCloseSocket() called
[junit] 2016-07-03 07:27:57,759 [myid:] - INFO  [main:PortAssignment@85] - 
Assigned port 11224 from range 11221 - 32767.
[junit] 2016-07-03 07:27:57,759 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@82] - Memory used 11998
[junit] 2016-07-03 07:27:57,759 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@87] - Number of threads 8
[junit] 2016-07-03 07:27:57,760 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@102] - FINISHED TEST METHOD 
testZooKeeperWithCustomHostProvider
[junit] 2016-07-03 07:27:57,760 [myid:] - INFO  [main:ZKTestCase$1@65] - 
SUCCEEDED testZooKeeperWithCustomHostProvider
[junit] 2016-07-03 07:27:57,760 [myid:] - INFO  [main:ZKTestCase$1@60] - 
FINISHED testZooKeeperWithCustomHostProvider
[junit] 2016-07-03 07:27:58,142 [myid:127.0.0.1:11223] - INFO  
[main-SendThread(127.0.0.1:11223):ClientCnxn$SendThread@1113] - Opening socket 
connection to server 127.0.0.1/127.0.0.1:11223. Will not attempt to 
authenticate using SASL (unknown error)
[junit] 2016-07-03 07:27:58,142 [myid:127.0.0.1:2181] - INFO  
[main-SendThread(127.0.0.1:2181):ClientCnxn$SendThread@1113] - Opening socket 
connection to server /127.0.0.1:2181. Will not attempt to authenticate using 
SASL (unknown error)
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 3.512 sec
[junit] 2016-07-03 07:28:08,136 [myid:] - INFO  
[main:JUnit4ZKTestRunner@47] - No test.method specified. using default methods.
[junit] Running org.apache.zookeeper.MultiResponseTest
[junit] 2016-07-03 07:28:09,001 [myid:] - INFO  
[main:JUnit4ZKTestRunner@47] - No test.method specified. using default methods.
[junit] 2016-07-03 07:28:09,153 [myid:] - INFO  [main:ZKTestCase$1@55] - 
STARTING testEmptyRoundTrip
[junit] 2016-07-03 07:28:09,158 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@77] - RUNNING TEST METHOD 
testEmptyRoundTrip
[junit] 2016-07-03 07:28:09,578 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@82] - Memory used 9853
[junit] 2016-07-03 07:28:09,578 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@87] - Number of threads 4
[junit] 2016-07-03 07:28:09,578 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@102] - FINISHED TEST METHOD 
testEmptyRoundTrip
[junit] 2016-07-03 07:28:09,579 [myid:] - INFO  [main:ZKTestCase$1@65] - 
SUCCEEDED testEmptyRoundTrip
[junit] 2016-07-03 07:28:09,579 [myid:] - INFO  [main:ZKTestCase$1@60] - 
FINISHED testEmptyRoundTrip
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 1.666 sec
[junit] 2016-07-03 07:28:20,744 [myid:] - INFO  
[main:JUnit4ZKTestRunner@47] - No test.method specified. using default methods.
[junit] Running org.apache.zookeeper.MultiTransactionRecordTest
[junit] 2016-07-03 07:28:23,934 [myid:] - INFO  
[main:JUnit4ZKTestRunner@47] - No test.method specified. using default methods.
[junit] 2016-07-03 07:28:24,867 [myid:] - INFO  [main:ZKTestCase$1@55] - 
STARTING testEmptyRoundTrip
[junit] 2016-07-03 07:28:24,895 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@77] - RUNNING TEST METHOD 
testEmptyRoundTrip
[junit] 2016-07-03 07:28:25,079 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@82] - Memory used 9525
[junit] 2016-07-03 07:28:25,079 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@87] - Number of threads 4
[junit] 2016-07-03 07:28:25,079 [myid:] - INFO  
[main:JUnit4ZK