[jira] [Commented] (ZOOKEEPER-1506) Re-try DNS hostname - IP resolution if node connection fails
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14386072#comment-14386072 ] Rakesh R commented on ZOOKEEPER-1506: - Thanks [~michim] for the fix. +1 latest patch looks good to me. Re-try DNS hostname - IP resolution if node connection fails - Key: ZOOKEEPER-1506 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1506 Project: ZooKeeper Issue Type: Improvement Components: server Affects Versions: 3.4.5 Environment: Ubuntu 11.04 64-bit Reporter: Mike Heffner Assignee: Michael Lasevich Priority: Critical Labels: patch Fix For: 3.4.7, 3.5.1, 3.6.0 Attachments: ZOOKEEPER-1506.patch, ZOOKEEPER-1506.patch, ZOOKEEPER-1506.patch, ZOOKEEPER-1506.patch, ZOOKEEPER-1506.patch, ZOOKEEPER-1506.patch, ZOOKEEPER-1506.patch, zk-dns-caching-refresh.patch In our zoo.cfg we use hostnames to identify the ZK servers that are part of an ensemble. These hostnames are configured with a low (= 60s) TTL and the IP address they map to can and does change. Our procedure for replacing/upgrading a ZK node is to boot an entirely new instance and remap the hostname to the new instance's IP address. Our expectation is that when the original ZK node is terminated/shutdown, the remaining nodes in the ensemble would reconnect to the new instance. However, what we are noticing is that the remaining ZK nodes do not attempt to re-resolve the hostname-IP mapping for the new server. Once the original ZK node is terminated, the existing servers continue to attempt contacting it at the old IP address. It would be great if the ZK servers could try to re-resolve the hostname when attempting to connect to a lost ZK server, instead of caching the lookup indefinitely. Currently we must do a rolling restart of the ZK ensemble after swapping a node -- which at three nodes means we periodically lose quorum. The exact method we are following is to boot new instances in EC2 and attach one, of a set of three, Elastic IP address. External to EC2 this IP address remains the same and maps to whatever instance it is attached to. Internal to EC2, the elastic IP hostname has a TTL of about 45-60 seconds and is remapped to the internal (10.x.y.z) address of the instance it is attached to. Therefore, in our case we would like ZK to pickup the new 10.x.y.z address that the elastic IP hostname gets mapped to and reconnect appropriately. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: Time for a 3.5.1-alpha release?
Hi Michi, Sure, I'm happy to help you to resolve this. Let me have a look at the patch. Regards, Rakesh On Mon, Mar 30, 2015 at 5:15 AM, Michi Mutsuzaki mi...@cs.stanford.edu wrote: I addressed comments from Camille and Flavio in ZOOKEEPER-1506. Could somebody check this patch in? https://issues.apache.org/jira/browse/ZOOKEEPER-1506 On Sun, Mar 22, 2015 at 3:53 PM, Michi Mutsuzaki mi...@cs.stanford.edu wrote: Thanks Rakesh, I'll work with Pat to prepare a release once ZOOKEEPER-1506 goes in. On Thu, Mar 19, 2015 at 11:10 PM, Rakesh R rake...@huawei.com wrote: FYI: We have done ZOOKEEPER-2107 and ZOOKEEPER-2125. ZOOKEEPER-1506 is pending. Cheers, Rakesh -Original Message- From: mutsuz...@gmail.com [mailto:mutsuz...@gmail.com] On Behalf Of Michi Mutsuzaki Sent: 15 March 2015 13:57 To: dev@zookeeper.apache.org Subject: Re: Time for a 3.5.1-alpha release? I think we are good to go once we get in these 3 patch-availables: https://issues.apache.org/jira/browse/ZOOKEEPER-1506 https://issues.apache.org/jira/browse/ZOOKEEPER-2107 https://issues.apache.org/jira/browse/ZOOKEEPER-2125 On Fri, Mar 13, 2015 at 4:30 PM, Patrick Hunt ph...@apache.org wrote: Hi folks, any thoughts on when we should cut a release? Note: Michi expressed interest in being the release manager for this release, so I've handed over the token to him. I will be mentoring him through the process, so I'll still be around. Patrick On Wed, Mar 11, 2015 at 10:32 PM, Rakesh R rake...@huawei.com wrote: Thank you Flavio for helping us. I will wait to see your feedback. Thanks, Rakesh 本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁 止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中 的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！ This e-mail and its attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it! From: Flavio Junqueira [mailto:fpjunque...@yahoo.com] Sent: 12 March 2015 02:09 To: dev@zookeeper.apache.org; mi...@cs.stanford.edu; Rakesh R Subject: Re: Time for a 3.5.1-alpha release? We should be able to have it in before the end of this week. I'm currently reviewing it. -Flavio On Wednesday, March 11, 2015 6:03 PM, Hongchao Deng fengjingc...@hotmail.commailto:fengjingc...@hotmail.com wrote: I think we can cut 3.5.1 for ZOOKEEPER-2125 regarding SSL. The auth would take too much time.Folks, please help push ZOOKEEPER-2125 and move this forward :) - Hongchao Deng From: rake...@huawei.commailto:rake...@huawei.com To: dev@zookeeper.apache.orgmailto:dev@zookeeper.apache.org; mi...@cs.stanford.edumailto:mi...@cs.stanford.edu Subject: RE: Time for a 3.5.1-alpha release? Date: Wed, 11 Mar 2015 09:54:01 + Hongchao/Rakesh, do you think the SSL patch should go in to 3.5.1? Thanks Michi for pointing this. Right now we have agreed upon ZOOKEEPER-2125. Major work will be finished with this jira, will push this in if nobody complains/comments. Still there are few more sub-tasks to be completed. Will try best and see the progress in this week. I feel based on that will take a decision. Is that ok? -Rakesh -Original Message- From: mutsuz...@gmail.commailto:mutsuz...@gmail.com [mailto:mutsuz...@gmail.commailto:mutsuz...@gmail.com] On Behalf Of Michi Mutsuzaki Sent: 10 March 2015 12:10 To: dev@zookeeper.apache.orgmailto:dev@zookeeper.apache.org Subject: Re: Time for a 3.5.1-alpha release? It would be great if somebody can review ZOOKEEPER-1506. Hongchao/Rakesh, do you think the SSL patch should go in to 3.5.1? On Mon, Mar 9, 2015 at 7:44 PM, Patrick Hunt ph...@apache.org mailto:ph...@apache.org wrote: Hi folks, just checking in. Any reason we shouldn't do a release in the near future? Anything pending that absolutely needs to get in? Patrick On Fri, Feb 6, 2015 at 9:15 AM, Patrick Hunt ph...@apache.org mailto:ph...@apache.org wrote: Sounds reasonable. Let's try to get these in, but depending on how much progress we make we might need to cut off at some point an push a release. They can always catch the next train. I'll try to update the jira list over the weekend, clean them up and see where we are. Patrick On Thu, Feb 5, 2015 at 9:39 PM, Michi Mutsuzaki mi...@cs.stanford.edumailto:mi...@cs.stanford.edu wrote: I'd like to get ZOOKEEPER-1506 in. On Thu, Feb 5, 2015 at 1:25 PM, Flavio Junqueira fpjunque...@yahoo.commailto:fpjunque...@yahoo.com wrote: I'd like to see the SSL work in for the next
[jira] [Resolved] (ZOOKEEPER-2080) ReconfigRecoveryTest fails intermittently
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Yu resolved ZOOKEEPER-2080.
---
Resolution: Cannot Reproduce
ReconfigRecoveryTest fails intermittently
-
Key: ZOOKEEPER-2080
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2080
Project: ZooKeeper
Issue Type: Sub-task
Reporter: Ted Yu
Priority: Minor
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] [Commented] (ZOOKEEPER-2123) Provide implementation of X509 AuthenticationProvider
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14385711#comment-14385711 ] Hudson commented on ZOOKEEPER-2123: --- SUCCESS: Integrated in ZooKeeper-trunk #2644 (See [https://builds.apache.org/job/ZooKeeper-trunk/2644/]) ZOOKEEPER-2123 Provide implementation of X509 AuthenticationProvider(Ian Dimayuga via rakeshr) (rakeshr: http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1669825) * /zookeeper/trunk/CHANGES.txt * /zookeeper/trunk/src/java/main/org/apache/zookeeper/ZooKeeperMain.java * /zookeeper/trunk/src/java/main/org/apache/zookeeper/client/FourLetterWordMain.java * /zookeeper/trunk/src/java/main/org/apache/zookeeper/common/X509Util.java * /zookeeper/trunk/src/java/main/org/apache/zookeeper/server/NIOServerCnxn.java * /zookeeper/trunk/src/java/main/org/apache/zookeeper/server/NettyServerCnxn.java * /zookeeper/trunk/src/java/main/org/apache/zookeeper/server/NettyServerCnxnFactory.java * /zookeeper/trunk/src/java/main/org/apache/zookeeper/server/ServerCnxn.java * /zookeeper/trunk/src/java/main/org/apache/zookeeper/server/ServerCnxnFactory.java * /zookeeper/trunk/src/java/main/org/apache/zookeeper/server/auth/ProviderRegistry.java * /zookeeper/trunk/src/java/main/org/apache/zookeeper/server/auth/X509AuthenticationProvider.java * /zookeeper/trunk/src/java/test/org/apache/zookeeper/server/MockServerCnxn.java * /zookeeper/trunk/src/java/test/org/apache/zookeeper/test/ClientBase.java * /zookeeper/trunk/src/java/test/org/apache/zookeeper/test/FourLetterWordsQuorumTest.java * /zookeeper/trunk/src/java/test/org/apache/zookeeper/test/FourLetterWordsTest.java * /zookeeper/trunk/src/java/test/org/apache/zookeeper/test/SSLAuthTest.java * /zookeeper/trunk/src/java/test/org/apache/zookeeper/test/X509AuthTest.java Provide implementation of X509 AuthenticationProvider - Key: ZOOKEEPER-2123 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2123 Project: ZooKeeper Issue Type: Sub-task Reporter: Hongchao Deng Assignee: Ian Dimayuga Priority: Minor Fix For: 3.5.1, 3.6.0 Attachments: ZOOKEEPER-2123.patch, ZOOKEEPER-2123.patch, ZOOKEEPER-2123.patch, ZOOKEEPER-2123.patch, ZOOKEEPER-2123.patch, ZOOKEEPER-2123.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-2139) Zookeeper client configuration should not be java system property
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14385671#comment-14385671
]
surendra singh lilhore commented on ZOOKEEPER-2139:
---
Failed test case is not related to this patch and its passing locally.
Please review.
Zookeeper client configuration should not be java system property
-
Key: ZOOKEEPER-2139
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2139
Project: ZooKeeper
Issue Type: Improvement
Components: java client
Affects Versions: 3.5.0
Reporter: surendra singh lilhore
Assignee: surendra singh lilhore
Fix For: 3.5.1, 3.6.0
Attachments: ZOOKEEPER-2139.patch, ZOOKEEPER-2139_1.patch,
ZOOKEEPER-2139_2.patch
I have two ZK client in one JVM, one is secure client and second is normal
client (For non secure cluster).
zookeeper.sasl.client system property is true by default, because of this
my second client connection is failing.
We should pass all client configurations in client constructor like HDFS
client.
For example :
{code}
public ZooKeeper(String connectString, int sessionTimeout, Watcher watcher,
Configuration conf) throws IOException
{
..
..
}
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ZOOKEEPER-2126) ClientCnxn.close doesn't wait for eventThread exit which cause out of order log when close Zookeeper client session.
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14385674#comment-14385674
]
surendra singh lilhore commented on ZOOKEEPER-2126:
---
Build result is showing core test cases are failed but actually in test results
all the test cases are passed.
Please review.
ClientCnxn.close doesn't wait for eventThread exit which cause out of order
log when close Zookeeper client session.
Key: ZOOKEEPER-2126
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2126
Project: ZooKeeper
Issue Type: Improvement
Affects Versions: 3.6.0
Reporter: zhihai xu
Assignee: surendra singh lilhore
Attachments: ZOOKEEPER-2126.patch
We saw the following out of order log when close Zookeeper client session.
{code}
2015-02-16 06:01:12,985 INFO org.apache.zookeeper.ZooKeeper: Session:
0x24b8df4044005d4 closed
.
2015-02-16 06:01:12,995 INFO org.apache.zookeeper.ClientCnxn: EventThread
shut down
{code}
This logs are very confusing if a new Zookeeper client session is created
between these two logs. We may think new Zookeeper client session shutdown it
EventThread instead of the old closed Zookeeper client session.
Should we wait for sendThread and eventThread died in the ClientCnxn.close?
We can add the following code in ClientCnxn.close.
{code}
sendThread.join(timeout);
eventThread.join(timeout);
{code}
with the change, we won't interleave old closed session with new session.
We can also create a new close API to support this so we won't affect the old
code if people use old close API.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
ZooKeeper_branch34_jdk7 - Build # 840 - Still Failing
See https://builds.apache.org/job/ZooKeeper_branch34_jdk7/840/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 212669 lines...] [junit] 2015-03-29 09:37:46,102 [myid:] - INFO [main:JMXEnv@246] - expect:StandaloneServer_port [junit] 2015-03-29 09:37:46,103 [myid:] - INFO [main:JMXEnv@250] - found:StandaloneServer_port org.apache.ZooKeeperService:name0=StandaloneServer_port11221 [junit] 2015-03-29 09:37:46,103 [myid:] - INFO [main:ClientBase@490] - STOPPING server [junit] 2015-03-29 09:37:46,103 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@224] - NIOServerCnxn factory exited run method [junit] 2015-03-29 09:37:46,103 [myid:] - INFO [main:ZooKeeperServer@441] - shutting down [junit] 2015-03-29 09:37:46,104 [myid:] - INFO [main:SessionTrackerImpl@225] - Shutting down [junit] 2015-03-29 09:37:46,104 [myid:] - INFO [main:PrepRequestProcessor@760] - Shutting down [junit] 2015-03-29 09:37:46,104 [myid:] - INFO [main:SyncRequestProcessor@209] - Shutting down [junit] 2015-03-29 09:37:46,104 [myid:] - INFO [ProcessThread(sid:0 cport:11221)::PrepRequestProcessor@143] - PrepRequestProcessor exited loop! [junit] 2015-03-29 09:37:46,104 [myid:] - INFO [SyncThread:0:SyncRequestProcessor@187] - SyncRequestProcessor exited! [junit] 2015-03-29 09:37:46,105 [myid:] - INFO [main:FinalRequestProcessor@415] - shutdown of request processor complete [junit] 2015-03-29 09:37:46,105 [myid:] - INFO [main:FourLetterWordMain@43] - connecting to 127.0.0.1 11221 [junit] 2015-03-29 09:37:46,106 [myid:] - INFO [main:JMXEnv@146] - ensureOnly:[] [junit] 2015-03-29 09:37:46,107 [myid:] - INFO [main:ClientBase@443] - STARTING server [junit] 2015-03-29 09:37:46,108 [myid:] - INFO [main:ClientBase@364] - CREATING server instance 127.0.0.1:11221 [junit] 2015-03-29 09:37:46,108 [myid:] - INFO [main:NIOServerCnxnFactory@94] - binding to port 0.0.0.0/0.0.0.0:11221 [junit] 2015-03-29 09:37:46,108 [myid:] - INFO [main:ClientBase@339] - STARTING server instance 127.0.0.1:11221 [junit] 2015-03-29 09:37:46,109 [myid:] - INFO [main:ZooKeeperServer@162] - Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 6 datadir /home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_jdk7/branch-3.4/build/test/tmp/test1723347264573869527.junit.dir/version-2 snapdir /home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_jdk7/branch-3.4/build/test/tmp/test1723347264573869527.junit.dir/version-2 [junit] 2015-03-29 09:37:46,113 [myid:] - INFO [main:FourLetterWordMain@43] - connecting to 127.0.0.1 11221 [junit] 2015-03-29 09:37:46,113 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@197] - Accepted socket connection from /127.0.0.1:33254 [junit] 2015-03-29 09:37:46,113 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxn@827] - Processing stat command from /127.0.0.1:33254 [junit] 2015-03-29 09:37:46,114 [myid:] - INFO [Thread-4:NIOServerCnxn$StatCommand@663] - Stat command output [junit] 2015-03-29 09:37:46,114 [myid:] - INFO [Thread-4:NIOServerCnxn@1007] - Closed socket connection for client /127.0.0.1:33254 (no session established for client) [junit] 2015-03-29 09:37:46,114 [myid:] - INFO [main:JMXEnv@229] - ensureParent:[InMemoryDataTree, StandaloneServer_port] [junit] 2015-03-29 09:37:46,117 [myid:] - INFO [main:JMXEnv@246] - expect:InMemoryDataTree [junit] 2015-03-29 09:37:46,117 [myid:] - INFO [main:JMXEnv@250] - found:InMemoryDataTree org.apache.ZooKeeperService:name0=StandaloneServer_port11221,name1=InMemoryDataTree [junit] 2015-03-29 09:37:46,117 [myid:] - INFO [main:JMXEnv@246] - expect:StandaloneServer_port [junit] 2015-03-29 09:37:46,117 [myid:] - INFO [main:JMXEnv@250] - found:StandaloneServer_port org.apache.ZooKeeperService:name0=StandaloneServer_port11221 [junit] 2015-03-29 09:37:46,117 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@55] - Memory used 10472 [junit] 2015-03-29 09:37:46,118 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@60] - Number of threads 20 [junit] 2015-03-29 09:37:46,118 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@65] - FINISHED TEST METHOD testQuota [junit] 2015-03-29 09:37:46,118 [myid:] - INFO [main:ClientBase@520] - tearDown starting [junit] 2015-03-29 09:37:46,187 [myid:] - INFO [main:ZooKeeper@684] - Session: 0x14c64e4e9e8 closed [junit] 2015-03-29 09:37:46,187 [myid:] - INFO [main:ClientBase@490] - STOPPING server [junit] 2015-03-29 09:37:46,187 [myid:] - INFO [main-EventThread:ClientCnxn$EventThread@512] - EventThread shut down [junit] 2015-03-29 09:37:46,188 [myid:] - INFO
ZooKeeper_branch34_openjdk7 - Build # 830 - Still Failing
See https://builds.apache.org/job/ZooKeeper_branch34_openjdk7/830/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 213444 lines...] [junit] 2015-03-29 10:04:20,514 [myid:] - INFO [main:JMXEnv@246] - expect:StandaloneServer_port [junit] 2015-03-29 10:04:20,515 [myid:] - INFO [main:JMXEnv@250] - found:StandaloneServer_port org.apache.ZooKeeperService:name0=StandaloneServer_port11221 [junit] 2015-03-29 10:04:20,515 [myid:] - INFO [main:ClientBase@490] - STOPPING server [junit] 2015-03-29 10:04:20,515 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@224] - NIOServerCnxn factory exited run method [junit] 2015-03-29 10:04:20,515 [myid:] - INFO [main:ZooKeeperServer@441] - shutting down [junit] 2015-03-29 10:04:20,516 [myid:] - INFO [main:SessionTrackerImpl@225] - Shutting down [junit] 2015-03-29 10:04:20,516 [myid:] - INFO [main:PrepRequestProcessor@760] - Shutting down [junit] 2015-03-29 10:04:20,516 [myid:] - INFO [main:SyncRequestProcessor@209] - Shutting down [junit] 2015-03-29 10:04:20,516 [myid:] - INFO [ProcessThread(sid:0 cport:11221)::PrepRequestProcessor@143] - PrepRequestProcessor exited loop! [junit] 2015-03-29 10:04:20,516 [myid:] - INFO [SyncThread:0:SyncRequestProcessor@187] - SyncRequestProcessor exited! [junit] 2015-03-29 10:04:20,517 [myid:] - INFO [main:FinalRequestProcessor@415] - shutdown of request processor complete [junit] 2015-03-29 10:04:20,517 [myid:] - INFO [main:FourLetterWordMain@43] - connecting to 127.0.0.1 11221 [junit] 2015-03-29 10:04:20,518 [myid:] - INFO [main:JMXEnv@146] - ensureOnly:[] [junit] 2015-03-29 10:04:20,520 [myid:] - INFO [main:ClientBase@443] - STARTING server [junit] 2015-03-29 10:04:20,520 [myid:] - INFO [main:ClientBase@364] - CREATING server instance 127.0.0.1:11221 [junit] 2015-03-29 10:04:20,520 [myid:] - INFO [main:NIOServerCnxnFactory@94] - binding to port 0.0.0.0/0.0.0.0:11221 [junit] 2015-03-29 10:04:20,521 [myid:] - INFO [main:ClientBase@339] - STARTING server instance 127.0.0.1:11221 [junit] 2015-03-29 10:04:20,521 [myid:] - INFO [main:ZooKeeperServer@162] - Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 6 datadir /home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_openjdk7/branch-3.4/build/test/tmp/test5319052359157918282.junit.dir/version-2 snapdir /home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_openjdk7/branch-3.4/build/test/tmp/test5319052359157918282.junit.dir/version-2 [junit] 2015-03-29 10:04:20,526 [myid:] - INFO [main:FourLetterWordMain@43] - connecting to 127.0.0.1 11221 [junit] 2015-03-29 10:04:20,526 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@197] - Accepted socket connection from /127.0.0.1:37589 [junit] 2015-03-29 10:04:20,527 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxn@827] - Processing stat command from /127.0.0.1:37589 [junit] 2015-03-29 10:04:20,527 [myid:] - INFO [Thread-4:NIOServerCnxn$StatCommand@663] - Stat command output [junit] 2015-03-29 10:04:20,528 [myid:] - INFO [Thread-4:NIOServerCnxn@1007] - Closed socket connection for client /127.0.0.1:37589 (no session established for client) [junit] 2015-03-29 10:04:20,528 [myid:] - INFO [main:JMXEnv@229] - ensureParent:[InMemoryDataTree, StandaloneServer_port] [junit] 2015-03-29 10:04:20,530 [myid:] - INFO [main:JMXEnv@246] - expect:InMemoryDataTree [junit] 2015-03-29 10:04:20,531 [myid:] - INFO [main:JMXEnv@250] - found:InMemoryDataTree org.apache.ZooKeeperService:name0=StandaloneServer_port11221,name1=InMemoryDataTree [junit] 2015-03-29 10:04:20,531 [myid:] - INFO [main:JMXEnv@246] - expect:StandaloneServer_port [junit] 2015-03-29 10:04:20,531 [myid:] - INFO [main:JMXEnv@250] - found:StandaloneServer_port org.apache.ZooKeeperService:name0=StandaloneServer_port11221 [junit] 2015-03-29 10:04:20,531 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@55] - Memory used 32637 [junit] 2015-03-29 10:04:20,532 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@60] - Number of threads 20 [junit] 2015-03-29 10:04:20,532 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@65] - FINISHED TEST METHOD testQuota [junit] 2015-03-29 10:04:20,532 [myid:] - INFO [main:ClientBase@520] - tearDown starting [junit] 2015-03-29 10:04:20,598 [myid:] - INFO [main:ZooKeeper@684] - Session: 0x14c64fd3d90 closed [junit] 2015-03-29 10:04:20,598 [myid:] - INFO [main:ClientBase@490] - STOPPING server [junit] 2015-03-29 10:04:20,598 [myid:] - INFO [main-EventThread:ClientCnxn$EventThread@512] - EventThread shut down [junit] 2015-03-29 10:04:20,598 [myid:] - INFO
ZooKeeper-trunk-openjdk7 - Build # 764 - Failure
See https://builds.apache.org/job/ZooKeeper-trunk-openjdk7/764/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 121 lines...] [mkdir] Created dir: /x1/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-openjdk7/trunk/build/jute_compiler/org/apache/jute/compiler/generated [ivy:artifactproperty] DEPRECATED: 'ivy.conf.file' is deprecated, use 'ivy.settings.file' instead [ivy:artifactproperty] :: loading settings :: file = /x1/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-openjdk7/trunk/ivysettings.xml [move] Moving 1 file to /x1/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-openjdk7/trunk/build/lib [javacc] Java Compiler Compiler Version 5.0 (Parser Generator) [javacc] (type javacc with no arguments for help) [javacc] Reading from file /x1/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-openjdk7/trunk/src/java/main/org/apache/jute/compiler/generated/rcc.jj . . . [javacc] File TokenMgrError.java does not exist. Will create one. [javacc] File ParseException.java does not exist. Will create one. [javacc] File Token.java does not exist. Will create one. [javacc] File SimpleCharStream.java does not exist. Will create one. [javacc] Parser generated successfully. jute: [javac] Compiling 39 source files to /x1/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-openjdk7/trunk/build/classes compile_jute_uptodate: compile_jute: [mkdir] Created dir: /x1/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-openjdk7/trunk/src/java/generated [mkdir] Created dir: /x1/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-openjdk7/trunk/src/c/generated [java] ../../zookeeper.jute Parsed Successfully [java] ../../zookeeper.jute Parsed Successfully [touch] Creating /x1/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-openjdk7/trunk/src/java/generated/.generated ver-gen: [javac] Compiling 1 source file to /x1/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-openjdk7/trunk/build/classes svn-revision: [mkdir] Created dir: /x1/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-openjdk7/trunk/.revision version-info: process-template: build-generated: [javac] Compiling 60 source files to /x1/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-openjdk7/trunk/build/classes compile: [javac] Compiling 211 source files to /x1/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-openjdk7/trunk/build/classes [javac] /x1/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-openjdk7/trunk/src/java/main/org/apache/zookeeper/server/FinalRequestProcessor.java:134: error: unmappable character for encoding ASCII [javac] // was not being queued ??? ZOOKEEPER-558) properly. This happens, for example, [javac] ^ [javac] /x1/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-openjdk7/trunk/src/java/main/org/apache/zookeeper/server/FinalRequestProcessor.java:134: error: unmappable character for encoding ASCII [javac] // was not being queued ??? ZOOKEEPER-558) properly. This happens, for example, [javac] ^ [javac] /x1/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-openjdk7/trunk/src/java/main/org/apache/zookeeper/server/FinalRequestProcessor.java:134: error: unmappable character for encoding ASCII [javac] // was not being queued ??? ZOOKEEPER-558) properly. This happens, for example, [javac] ^ [javac] 3 errors BUILD FAILED /x1/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-openjdk7/trunk/build.xml:433: Compile failed; see the compiler error output for details. Total time: 17 seconds Build step 'Invoke Ant' marked build as failure Recording test results Email was triggered for: Failure Sending email for trigger: Failure ### ## FAILED TESTS (if any) ## No tests ran.
Re: Time for a 3.5.1-alpha release?
I addressed comments from Camille and Flavio in ZOOKEEPER-1506. Could somebody check this patch in? https://issues.apache.org/jira/browse/ZOOKEEPER-1506 On Sun, Mar 22, 2015 at 3:53 PM, Michi Mutsuzaki mi...@cs.stanford.edu wrote: Thanks Rakesh, I'll work with Pat to prepare a release once ZOOKEEPER-1506 goes in. On Thu, Mar 19, 2015 at 11:10 PM, Rakesh R rake...@huawei.com wrote: FYI: We have done ZOOKEEPER-2107 and ZOOKEEPER-2125. ZOOKEEPER-1506 is pending. Cheers, Rakesh -Original Message- From: mutsuz...@gmail.com [mailto:mutsuz...@gmail.com] On Behalf Of Michi Mutsuzaki Sent: 15 March 2015 13:57 To: dev@zookeeper.apache.org Subject: Re: Time for a 3.5.1-alpha release? I think we are good to go once we get in these 3 patch-availables: https://issues.apache.org/jira/browse/ZOOKEEPER-1506 https://issues.apache.org/jira/browse/ZOOKEEPER-2107 https://issues.apache.org/jira/browse/ZOOKEEPER-2125 On Fri, Mar 13, 2015 at 4:30 PM, Patrick Hunt ph...@apache.org wrote: Hi folks, any thoughts on when we should cut a release? Note: Michi expressed interest in being the release manager for this release, so I've handed over the token to him. I will be mentoring him through the process, so I'll still be around. Patrick On Wed, Mar 11, 2015 at 10:32 PM, Rakesh R rake...@huawei.com wrote: Thank you Flavio for helping us. I will wait to see your feedback. Thanks, Rakesh 本邮件及其附件含有华为公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁 止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中 的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！ This e-mail and its attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it! From: Flavio Junqueira [mailto:fpjunque...@yahoo.com] Sent: 12 March 2015 02:09 To: dev@zookeeper.apache.org; mi...@cs.stanford.edu; Rakesh R Subject: Re: Time for a 3.5.1-alpha release? We should be able to have it in before the end of this week. I'm currently reviewing it. -Flavio On Wednesday, March 11, 2015 6:03 PM, Hongchao Deng fengjingc...@hotmail.commailto:fengjingc...@hotmail.com wrote: I think we can cut 3.5.1 for ZOOKEEPER-2125 regarding SSL. The auth would take too much time.Folks, please help push ZOOKEEPER-2125 and move this forward :) - Hongchao Deng From: rake...@huawei.commailto:rake...@huawei.com To: dev@zookeeper.apache.orgmailto:dev@zookeeper.apache.org; mi...@cs.stanford.edumailto:mi...@cs.stanford.edu Subject: RE: Time for a 3.5.1-alpha release? Date: Wed, 11 Mar 2015 09:54:01 + Hongchao/Rakesh, do you think the SSL patch should go in to 3.5.1? Thanks Michi for pointing this. Right now we have agreed upon ZOOKEEPER-2125. Major work will be finished with this jira, will push this in if nobody complains/comments. Still there are few more sub-tasks to be completed. Will try best and see the progress in this week. I feel based on that will take a decision. Is that ok? -Rakesh -Original Message- From: mutsuz...@gmail.commailto:mutsuz...@gmail.com [mailto:mutsuz...@gmail.commailto:mutsuz...@gmail.com] On Behalf Of Michi Mutsuzaki Sent: 10 March 2015 12:10 To: dev@zookeeper.apache.orgmailto:dev@zookeeper.apache.org Subject: Re: Time for a 3.5.1-alpha release? It would be great if somebody can review ZOOKEEPER-1506. Hongchao/Rakesh, do you think the SSL patch should go in to 3.5.1? On Mon, Mar 9, 2015 at 7:44 PM, Patrick Hunt ph...@apache.orgmailto:ph...@apache.org wrote: Hi folks, just checking in. Any reason we shouldn't do a release in the near future? Anything pending that absolutely needs to get in? Patrick On Fri, Feb 6, 2015 at 9:15 AM, Patrick Hunt ph...@apache.orgmailto:ph...@apache.org wrote: Sounds reasonable. Let's try to get these in, but depending on how much progress we make we might need to cut off at some point an push a release. They can always catch the next train. I'll try to update the jira list over the weekend, clean them up and see where we are. Patrick On Thu, Feb 5, 2015 at 9:39 PM, Michi Mutsuzaki mi...@cs.stanford.edumailto:mi...@cs.stanford.edu wrote: I'd like to get ZOOKEEPER-1506 in. On Thu, Feb 5, 2015 at 1:25 PM, Flavio Junqueira fpjunque...@yahoo.commailto:fpjunque...@yahoo.com wrote: I'd like to see the SSL work in for the next release. -Flavio On 05 Feb 2015, at 19:34, Raúl Gutiérrez Segalés r...@itevenworks.netmailto:r...@itevenworks.net wrote: +1 It would be nice, but they are not blockers, to get these in: https://issues.apache.org/jira/browse/ZOOKEEPER-1998
