[jira] [Updated] (ZOOKEEPER-938) Support Kerberos authentication of clients.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eugene Koontz updated ZOOKEEPER-938: Attachment: ZOOKEEPER-938.patch Address Benjamin Reed's feedback: -Remove OpCode.sasl from Request.java since it's not needed there. -in ZooKeeperServer, move SASL-related server-side code into separate method processSasl() Support Kerberos authentication of clients. --- Key: ZOOKEEPER-938 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-938 Project: ZooKeeper Issue Type: New Feature Components: java client, server Reporter: Eugene Koontz Assignee: Eugene Koontz Fix For: 3.4.0, 3.5.0 Attachments: NIOServerCnxn.patch, ZOOKEEPER-938.patch, ZOOKEEPER-938.patch, ZOOKEEPER-938.patch, ZOOKEEPER-938.patch, ZOOKEEPER-938.patch, ZOOKEEPER-938.patch, ZOOKEEPER-938.patch, ZOOKEEPER-938.patch, ZOOKEEPER-938.patch, ZOOKEEPER-938.patch, ZOOKEEPER-938.patch, ZOOKEEPER-938.patch, ZOOKEEPER-938.patch, jaas.conf, sasl.patch Support Kerberos authentication of clients. The following usage would let an admin use Kerberos authentication to assign ACLs to authenticated clients. 1. Admin logs into zookeeper (not necessarily through Kerberos however). 2. Admin decides that a new node called '/mynode' should be owned by the user 'zkclient' and have full permissions on this. 3. Admin does: zk create /mynode content sasl:zkcli...@foofers.org:cdrwa 4. User 'zkclient' logins to kerberos using the command line utility 'kinit'. 5. User connects to zookeeper server using a Kerberos-enabled version of zkClient (ZookeeperMain). 6. Behind the scenes, the client and server exchange authentication information. User is now authenticated as 'zkclient'. 7. User accesses /mynode with permissions 'cdrwa'. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (ZOOKEEPER-938) Support Kerberos authentication of clients.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13081866#comment-13081866 ] Eugene Koontz commented on ZOOKEEPER-938: - Hi Benjamin, Thanks a lot for your feedback! I addressed the two cleanup issues in a new patch. Regarding the sun.* classes, these are only needed to determine the default Kerberos realm from the system's Kerberos conf file (usually in /etc/krb5.conf). I think we can use the java.security.* functionality to replace sun.security.*: http://download.oracle.com/javase/1.4.2/docs/guide/security/jgss/tutorials/KerberosReq.html I will try this out and update the patch if this will work. Support Kerberos authentication of clients. --- Key: ZOOKEEPER-938 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-938 Project: ZooKeeper Issue Type: New Feature Components: java client, server Reporter: Eugene Koontz Assignee: Eugene Koontz Fix For: 3.4.0, 3.5.0 Attachments: NIOServerCnxn.patch, ZOOKEEPER-938.patch, ZOOKEEPER-938.patch, ZOOKEEPER-938.patch, ZOOKEEPER-938.patch, ZOOKEEPER-938.patch, ZOOKEEPER-938.patch, ZOOKEEPER-938.patch, ZOOKEEPER-938.patch, ZOOKEEPER-938.patch, ZOOKEEPER-938.patch, ZOOKEEPER-938.patch, ZOOKEEPER-938.patch, ZOOKEEPER-938.patch, jaas.conf, sasl.patch Support Kerberos authentication of clients. The following usage would let an admin use Kerberos authentication to assign ACLs to authenticated clients. 1. Admin logs into zookeeper (not necessarily through Kerberos however). 2. Admin decides that a new node called '/mynode' should be owned by the user 'zkclient' and have full permissions on this. 3. Admin does: zk create /mynode content sasl:zkcli...@foofers.org:cdrwa 4. User 'zkclient' logins to kerberos using the command line utility 'kinit'. 5. User connects to zookeeper server using a Kerberos-enabled version of zkClient (ZookeeperMain). 6. Behind the scenes, the client and server exchange authentication information. User is now authenticated as 'zkclient'. 7. User accesses /mynode with permissions 'cdrwa'. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (ZOOKEEPER-938) Support Kerberos authentication of clients.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13081939#comment-13081939 ] Eugene Koontz commented on ZOOKEEPER-938: - Hi Benjamin, Unfortunately I couldn't find support for obtaining the default Kerberos realm in java.security or javax.security. (In fact, it seems that javax.security uses sun.security internally, for example: http://www.java2s.com/Open-Source/Java-Document/6.0-JDK-Core/security/javax/security/auth/kerberos/KerberosPrincipal.java.htm. (see import sun.security.krb5.Asn1Exception; in the source code)). So I don't see any way around using the sun.* classes. -Eugene Support Kerberos authentication of clients. --- Key: ZOOKEEPER-938 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-938 Project: ZooKeeper Issue Type: New Feature Components: java client, server Reporter: Eugene Koontz Assignee: Eugene Koontz Fix For: 3.4.0, 3.5.0 Attachments: NIOServerCnxn.patch, ZOOKEEPER-938.patch, ZOOKEEPER-938.patch, ZOOKEEPER-938.patch, ZOOKEEPER-938.patch, ZOOKEEPER-938.patch, ZOOKEEPER-938.patch, ZOOKEEPER-938.patch, ZOOKEEPER-938.patch, ZOOKEEPER-938.patch, ZOOKEEPER-938.patch, ZOOKEEPER-938.patch, ZOOKEEPER-938.patch, ZOOKEEPER-938.patch, jaas.conf, sasl.patch Support Kerberos authentication of clients. The following usage would let an admin use Kerberos authentication to assign ACLs to authenticated clients. 1. Admin logs into zookeeper (not necessarily through Kerberos however). 2. Admin decides that a new node called '/mynode' should be owned by the user 'zkclient' and have full permissions on this. 3. Admin does: zk create /mynode content sasl:zkcli...@foofers.org:cdrwa 4. User 'zkclient' logins to kerberos using the command line utility 'kinit'. 5. User connects to zookeeper server using a Kerberos-enabled version of zkClient (ZookeeperMain). 6. Behind the scenes, the client and server exchange authentication information. User is now authenticated as 'zkclient'. 7. User accesses /mynode with permissions 'cdrwa'. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (ZOOKEEPER-1145) ObserverTest.testObserver fails at particular point after several runs of ant junt.run -Dtestcase=ObserverTest
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13082015#comment-13082015 ] Eugene Koontz commented on ZOOKEEPER-1145: -- Hi Vishal, Good news. I tried trunk today (commit e9373536) with your patch on a EC-2 m2.xlarge. I ran ObserverTest 300 times and the whole ant test 3 times. No errors. ObserverTest.testObserver fails at particular point after several runs of ant junt.run -Dtestcase=ObserverTest -- Key: ZOOKEEPER-1145 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1145 Project: ZooKeeper Issue Type: Bug Affects Versions: 3.4.0 Reporter: Eugene Koontz Assignee: Vishal Kher Priority: Blocker Fix For: 3.4.0 Attachments: out.txt, repeat.sh Use the attached repeat.sh to run ObserverTest repeatedly by doing: src/repeat.sh ObserverTest The test will will fail eventually after a few iterations; should be only a few minutes. The line that fails in the test is: zk = new ZooKeeper(127.0.0.1: + CLIENT_PORT_OBS, ClientBase.CONNECTION_TIMEOUT, this); Attached as out.txt is the output showing a successful run, for comparison, followed by a failed run. Note that in the seconds before the test fails, in the following lines, that there is a 24 second gap in time (between 22:13:02 and 22:13:26): bq. [junit] 2011-08-03 22:13:02,167 [myid:3] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11229:ZooKeeperServer@833] - Client attempting to establish new session at /127.0.0.1:46929 [junit] 2011-08-03 22:13:26,003 [myid:2] - INFO [QuorumPeer[myid=2]/0:0:0:0:0:0:0:0:11228:Leader@419] - Shutting down [junit] 2011-08-03 22:13:26,003 [myid:2] - INFO [QuorumPeer[myid=2]/0:0:0:0:0:0:0:0:11228:Leader@425] - Shutdown called [junit] java.lang.Exception: shutdown Leader! reason: Only 0 followers, need 1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
ZooKeeper-trunk - Build # 1258 - Failure
See https://builds.apache.org/job/ZooKeeper-trunk/1258/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 1122 lines...]
AUhudsonPatchQueueAdmin.sh
AUprocessHadoopPatchEmail.sh
A README.txt
A test-patch
A test-patch/test-patch.sh
At revision 1155988
No emails were triggered.
[ZooKeeper-trunk] $ /bin/bash /tmp/hudson3188972585120407500.sh
1024
==
==
CLEAN: cleaning workspace
==
==
Error: JAVA_HOME is not defined correctly.
We cannot execute /home/hudson/tools/java/latest1.6/bin/java
==
==
BUILD: ant hudson-test-trunk -Dtest.junit.output.format=xml -Dtest.output=yes
-Dfindbugs.home=${FINDBUGS_HOME} -Dforrest.home=${FORREST_HOME}
-Djava5.home=${JAVA5_HOME}
==
==
Error: JAVA_HOME is not defined correctly.
We cannot execute /home/hudson/tools/java/latest1.6/bin/java
==
==
STORE: saving artifacts
==
==
mv: cannot stat `build/*.tar.gz': No such file or directory
mv: cannot stat `build/*.jar': No such file or directory
mv: cannot stat `build/test/findbugs': No such file or directory
mv: cannot stat `build/docs/api': No such file or directory
Build Failed
[FINDBUGS] Skipping publisher since build result is FAILURE
[WARNINGS] Skipping publisher since build result is FAILURE
Recording fingerprints
Archiving artifacts
Recording test results
Publishing Javadoc
Updating ZOOKEEPER-1090
Updating ZOOKEEPER-1138
Updating ZOOKEEPER-1139
Updating ZOOKEEPER-1076
Publishing Clover coverage report...
No Clover report will be published due to a Build Failure
Email was triggered for: Failure
Sending email for trigger: Failure
###
## FAILED TESTS (if any)
##
No tests ran.
[jira] [Commented] (ZOOKEEPER-1138) release audit failing for a number of new files
[
https://issues.apache.org/jira/browse/ZOOKEEPER-1138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13082062#comment-13082062
]
Hudson commented on ZOOKEEPER-1138:
---
Integrated in ZooKeeper-trunk #1258 (See
[https://builds.apache.org/job/ZooKeeper-trunk/1258/])
ZOOKEEPER-1138. release audit failing for a number of new files. (phunt via
mahadev) - forgot file
ZOOKEEPER-1138. release audit failing for a number of new files. (phunt via
mahadev)
mahadev :
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1152033
Files :
* /zookeeper/trunk/src/c/NOTICE.txt
mahadev :
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1152018
Files :
*
/zookeeper/trunk/src/java/test/org/apache/zookeeper/server/quorum/LearnerTest.java
* /zookeeper/trunk/src/contrib/huebrowser/zkui/src/zkui/static/js/package.yml
* /zookeeper/trunk/src/contrib/zooinspector/config/defaultNodeVeiwers.cfg
* /zookeeper/trunk/NOTICE.txt
*
/zookeeper/trunk/src/java/test/org/apache/zookeeper/MultiTransactionRecordTest.java
* /zookeeper/trunk/CHANGES.txt
* /zookeeper/trunk/build.xml
* /zookeeper/trunk/src/contrib/huebrowser/zkui/src/zkui/static/help/index.html
* /zookeeper/trunk/src/contrib/zooinspector/config/defaultConnectionSettings.cfg
release audit failing for a number of new files
---
Key: ZOOKEEPER-1138
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1138
Project: ZooKeeper
Issue Type: Bug
Affects Versions: 3.4.0
Reporter: Patrick Hunt
Assignee: Patrick Hunt
Priority: Blocker
Fix For: 3.4.0
Attachments: ZOOKEEPER-1138.patch
I'm seeing a number of problems in the release audit output for 3.4.0, these
must be fixed before 3.4.0 release:
{noformat}
[rat:report] !?
/grid/0/hudson/hudson-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/build/zookeeper-3.4.0/contrib/ZooInspector/config/defaultConnectionSettings.cfg
[rat:report] !?
/grid/0/hudson/hudson-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/build/zookeeper-3.4.0/contrib/ZooInspector/config/defaultNodeVeiwers.cfg
[rat:report] !?
/grid/0/hudson/hudson-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/build/zookeeper-3.4.0/contrib/ZooInspector/licences/epl-v10.html
[rat:report] !?
/grid/0/hudson/hudson-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/build/zookeeper-3.4.0/src/c/Cli.vcproj
[rat:report] !?
/grid/0/hudson/hudson-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/build/zookeeper-3.4.0/src/c/include/winconfig.h
[rat:report] !?
/grid/0/hudson/hudson-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/build/zookeeper-3.4.0/src/c/include/winstdint.h
[rat:report] !?
/grid/0/hudson/hudson-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/build/zookeeper-3.4.0/src/c/zookeeper.sln
[rat:report] !?
/grid/0/hudson/hudson-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/build/zookeeper-3.4.0/src/c/zookeeper.vcproj
[rat:report] !?
/grid/0/hudson/hudson-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/build/zookeeper-3.4.0/src/contrib/huebrowser/zkui/src/zkui/static/help/index.html
[rat:report] !?
/grid/0/hudson/hudson-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/build/zookeeper-3.4.0/src/contrib/huebrowser/zkui/src/zkui/static/js/package.yml
[rat:report] !?
/grid/0/hudson/hudson-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/build/zookeeper-3.4.0/src/contrib/loggraph/web/org/apache/zookeeper/graph/log4j.properties
[rat:report] !?
/grid/0/hudson/hudson-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/build/zookeeper-3.4.0/src/contrib/loggraph/web/org/apache/zookeeper/graph/resources/date.format.js
[rat:report] !?
/grid/0/hudson/hudson-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/build/zookeeper-3.4.0/src/contrib/loggraph/web/org/apache/zookeeper/graph/resources/g.bar.js
[rat:report] !?
/grid/0/hudson/hudson-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/build/zookeeper-3.4.0/src/contrib/loggraph/web/org/apache/zookeeper/graph/resources/g.dot.js
[rat:report] !?
/grid/0/hudson/hudson-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/build/zookeeper-3.4.0/src/contrib/loggraph/web/org/apache/zookeeper/graph/resources/g.line.js
[rat:report] !?
/grid/0/hudson/hudson-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/build/zookeeper-3.4.0/src/contrib/loggraph/web/org/apache/zookeeper/graph/resources/g.pie.js
[rat:report] !?
/grid/0/hudson/hudson-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/build/zookeeper-3.4.0/src/contrib/loggraph/web/org/apache/zookeeper/graph/resources/g.raphael.js
[rat:report] !?
/grid/0/hudson/hudson-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/build/zookeeper-3.4.0/src/contrib/loggraph/web/org/apache/zookeeper/graph/resources/raphael.js
[rat:report]
[jira] [Commented] (ZOOKEEPER-1076) some quorum tests are unnecessarily extending QuorumBase
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13082064#comment-13082064 ] Hudson commented on ZOOKEEPER-1076: --- Integrated in ZooKeeper-trunk #1258 (See [https://builds.apache.org/job/ZooKeeper-trunk/1258/]) ZOOKEEPER-1076. some quorum tests are unnecessarily extending QuorumBase (phunt via mahadev) mahadev : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1152141 Files : * /zookeeper/trunk/src/java/test/org/apache/zookeeper/test/FollowerResyncConcurrencyTest.java * /zookeeper/trunk/src/java/test/org/apache/zookeeper/test/QuorumTest.java * /zookeeper/trunk/CHANGES.txt * /zookeeper/trunk/src/java/test/org/apache/zookeeper/test/ZkDatabaseCorruptionTest.java * /zookeeper/trunk/src/java/test/org/apache/zookeeper/test/QuorumHammerTest.java * /zookeeper/trunk/src/java/test/org/apache/zookeeper/test/ReadOnlyModeTest.java some quorum tests are unnecessarily extending QuorumBase Key: ZOOKEEPER-1076 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1076 Project: ZooKeeper Issue Type: Bug Components: tests Affects Versions: 3.4.0 Reporter: Patrick Hunt Assignee: Patrick Hunt Priority: Minor Fix For: 3.4.0 Attachments: ZOOKEEPER-1076.patch, ZOOKEEPER-1076.patch Some tests are unnecessarily extending QuorumBase. Typically this is not a big issue, but it may cause more servers than necessary to be started (harder to debug a failing test in particular). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (ZOOKEEPER-1139) jenkins is reporting two warnings, fix these
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13082063#comment-13082063 ] Hudson commented on ZOOKEEPER-1139: --- Integrated in ZooKeeper-trunk #1258 (See [https://builds.apache.org/job/ZooKeeper-trunk/1258/]) ZOOKEEPER-1139. jenkins is reporting two warnings, fix these (phunt via mahadev) mahadev : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1152036 Files : * /zookeeper/trunk/src/java/main/org/apache/zookeeper/Op.java * /zookeeper/trunk/CHANGES.txt * /zookeeper/trunk/src/java/main/org/apache/zookeeper/ClientWatchManager.java jenkins is reporting two warnings, fix these Key: ZOOKEEPER-1139 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1139 Project: ZooKeeper Issue Type: Bug Affects Versions: 3.4.0 Reporter: Patrick Hunt Assignee: Patrick Hunt Priority: Minor Fix For: 3.4.0 Attachments: ZOOKEEPER-1139.patch cleanup jenkins report, currently 2 compiler warnings being reported. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (ZOOKEEPER-1145) ObserverTest.testObserver fails at particular point after several runs of ant junt.run -Dtestcase=ObserverTest
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13082109#comment-13082109 ] Mahadev konar commented on ZOOKEEPER-1145: -- thats great news! ObserverTest.testObserver fails at particular point after several runs of ant junt.run -Dtestcase=ObserverTest -- Key: ZOOKEEPER-1145 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1145 Project: ZooKeeper Issue Type: Bug Affects Versions: 3.4.0 Reporter: Eugene Koontz Assignee: Vishal Kher Priority: Blocker Fix For: 3.4.0 Attachments: out.txt, repeat.sh Use the attached repeat.sh to run ObserverTest repeatedly by doing: src/repeat.sh ObserverTest The test will will fail eventually after a few iterations; should be only a few minutes. The line that fails in the test is: zk = new ZooKeeper(127.0.0.1: + CLIENT_PORT_OBS, ClientBase.CONNECTION_TIMEOUT, this); Attached as out.txt is the output showing a successful run, for comparison, followed by a failed run. Note that in the seconds before the test fails, in the following lines, that there is a 24 second gap in time (between 22:13:02 and 22:13:26): bq. [junit] 2011-08-03 22:13:02,167 [myid:3] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11229:ZooKeeperServer@833] - Client attempting to establish new session at /127.0.0.1:46929 [junit] 2011-08-03 22:13:26,003 [myid:2] - INFO [QuorumPeer[myid=2]/0:0:0:0:0:0:0:0:11228:Leader@419] - Shutting down [junit] 2011-08-03 22:13:26,003 [myid:2] - INFO [QuorumPeer[myid=2]/0:0:0:0:0:0:0:0:11228:Leader@425] - Shutdown called [junit] java.lang.Exception: shutdown Leader! reason: Only 0 followers, need 1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Hadoop build machine update
Thanks a lot Giri. I see something for ZK builds. Hopefully they'll be functional tomm. thanks mahadev On Tue, Aug 9, 2011 at 7:35 PM, Giridharan Kesavan gkesa...@hortonworks.com wrote: All, All the hudson slaves are back online. I was working on getting the build tools installed on all the new slaves and it looks like Its going to take some more time to change the build job configs before I could enable the pre-commit jobs. Will get the precommit and nightly build jobs back online tomorrow. -Giri On Tue, Aug 2, 2011 at 11:45 PM, Nigel Daley nda...@mac.com wrote: Great! Thanks for getting the info. Cheers, n. On Aug 2, 2011, at 8:05 PM, Eric Baldeschwieler wrote: Hi Folks, I've talked to the folks at Yahoo about the build machines and am happy to report that an end to the blackout is in sight. 1) They need to reimage the machines, which is in progress and machines should be restored within a week (pessimistically). 2) They plan to reach out to the apache infrastructure team and change the admin of these machines to remove yahoo from the admin loop. This should avoid future outages and give apache more flexibility in managing the machines. I'm told they will be posting more details today or tomorrow. Everyone there is committed to maintaining quality support for Apache and is concerned about the outage and making sure it does not repeat. Thanks, E14
RE: Hadoop build machine update
Hi Mahadev, Do we need to resubmit the patches which were uploaded last week? Or Hudson will pick them up automatically? -Original Message- From: Mahadev Konar [mailto:maha...@hortonworks.com] Sent: Wednesday, August 10, 2011 8:14 AM To: dev@zookeeper.apache.org; Giridharan Kesavan Subject: Re: Hadoop build machine update Thanks a lot Giri. I see something for ZK builds. Hopefully they'll be functional tomm. thanks mahadev On Tue, Aug 9, 2011 at 7:35 PM, Giridharan Kesavan gkesa...@hortonworks.com wrote: All, All the hudson slaves are back online. I was working on getting the build tools installed on all the new slaves and it looks like Its going to take some more time to change the build job configs before I could enable the pre-commit jobs. Will get the precommit and nightly build jobs back online tomorrow. -Giri On Tue, Aug 2, 2011 at 11:45 PM, Nigel Daley nda...@mac.com wrote: Great! Thanks for getting the info. Cheers, n. On Aug 2, 2011, at 8:05 PM, Eric Baldeschwieler wrote: Hi Folks, I've talked to the folks at Yahoo about the build machines and am happy to report that an end to the blackout is in sight. 1) They need to reimage the machines, which is in progress and machines should be restored within a week (pessimistically). 2) They plan to reach out to the apache infrastructure team and change the admin of these machines to remove yahoo from the admin loop. This should avoid future outages and give apache more flexibility in managing the machines. I'm told they will be posting more details today or tomorrow. Everyone there is committed to maintaining quality support for Apache and is concerned about the outage and making sure it does not repeat. Thanks, E14
[jira] [Commented] (ZOOKEEPER-1140) server shutdown is not stopping threads
[
https://issues.apache.org/jira/browse/ZOOKEEPER-1140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13082146#comment-13082146
]
Laxman commented on ZOOKEEPER-1140:
---
Thread [Sender-/127.0.0.1:3084] (Running)
When I observed QuorumZxidSyncTest, the above thread is also leaking in a
different scenario apart from ReadOnlyZKServer. Above mentioned thread will be
shutdown only if it receives proposalOfDeath.
We are queuing proposalOfDeath in finally block of LearnerHandler.run().
To summarize, proposalOfDeath may not queued up when LearnerHandler receives
IOException and other thread calling LearnerHandler.shutdown(). This leads to
failure of queuing the proposalOfDeath.
To solve this, can we add the proposalOfDeath in shutdown() rather in finally
block.
Anyways, this finding will solve one of the leaks. We still need to fix other
leaks caused by ROZK.
{quote}Just to see if I understand now, are you saying that the test is
spawning over one hundred servers because we are shutting before the server
actually starts? If so, then it is certainly a problem.{quote}
Yes. I will add more analysis and possibly patch today.
server shutdown is not stopping threads
---
Key: ZOOKEEPER-1140
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1140
Project: ZooKeeper
Issue Type: Bug
Components: server, tests
Affects Versions: 3.4.0
Reporter: Patrick Hunt
Priority: Blocker
Fix For: 3.4.0
Near the end of QuorumZxidSyncTest there are tons of threads running - 115
ProcessThread threads, similar numbers of SessionTracker.
Also I see ~100 ReadOnlyRequestProcessor - why is this running as a separate
thread? (henry/flavio?)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
