Success: ZOOKEEPER-1426 PreCommit Build #1158
Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-1426 Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1158/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 262391 lines...] [exec] BUILD SUCCESSFUL [exec] Total time: 0 seconds [exec] [exec] [exec] [exec] [exec] +1 overall. Here are the results of testing the latest attachment [exec] http://issues.apache.org/jira/secure/attachment/12539752/ZOOKEEPER-1426-3.patch [exec] against trunk revision 1368737. [exec] [exec] +1 @author. The patch does not contain any @author tags. [exec] [exec] +1 tests included. The patch appears to include 6 new or modified tests. [exec] [exec] +1 javadoc. The javadoc tool did not generate any warning messages. [exec] [exec] +1 javac. The applied patch does not increase the total number of javac compiler warnings. [exec] [exec] +1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings. [exec] [exec] +1 release audit. The applied patch does not increase the total number of release audit warnings. [exec] [exec] +1 core tests. The patch passed core unit tests. [exec] [exec] +1 contrib tests. The patch passed contrib unit tests. [exec] [exec] Test results: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1158//testReport/ [exec] Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1158//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html [exec] Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1158//console [exec] [exec] This message is automatically generated. [exec] [exec] [exec] == [exec] == [exec] Adding comment to Jira. [exec] == [exec] == [exec] [exec] [exec] Comment added. [exec] Kpr7602w8j logged out [exec] [exec] [exec] == [exec] == [exec] Finished build. [exec] == [exec] == [exec] [exec] BUILD SUCCESSFUL Total time: 27 minutes 26 seconds Archiving artifacts Recording test results Description set: ZOOKEEPER-1426 Email was triggered for: Success Sending email for trigger: Success ### ## FAILED TESTS (if any) ## All tests passed
[jira] [Commented] (ZOOKEEPER-1426) add version command to the zookeeper server
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13430788#comment-13430788 ] Hadoop QA commented on ZOOKEEPER-1426: -- +1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12539752/ZOOKEEPER-1426-3.patch against trunk revision 1368737. +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 6 new or modified tests. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. +1 core tests. The patch passed core unit tests. +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1158//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1158//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1158//console This message is automatically generated. > add version command to the zookeeper server > --- > > Key: ZOOKEEPER-1426 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1426 > Project: ZooKeeper > Issue Type: Improvement > Components: scripts, server >Affects Versions: 3.3.5 >Reporter: Patrick Hunt >Assignee: Eli Reisman > Labels: newbie, patch > Attachments: MAPREDUCE-4282-2.patch, ZOOKEEPER-1426-1.patch, > ZOOKEEPER-1426-2.patch, ZOOKEEPER-1426-3.patch > > > Add a version command to the zkServer.sh. > Hadoop does this by having a special main class: > org.apache.hadoop.util.VersionInfo > We could do something similar, hook it into our current version information > class (perhaps add main to that class). > Would also need to add a new "version" command to zkServer.sh that calls this. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (ZOOKEEPER-1426) add version command to the zookeeper server
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eli Reisman updated ZOOKEEPER-1426: --- Attachment: ZOOKEEPER-1426-3.patch > add version command to the zookeeper server > --- > > Key: ZOOKEEPER-1426 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1426 > Project: ZooKeeper > Issue Type: Improvement > Components: scripts, server >Affects Versions: 3.3.5 >Reporter: Patrick Hunt >Assignee: Eli Reisman > Labels: newbie, patch > Attachments: MAPREDUCE-4282-2.patch, ZOOKEEPER-1426-1.patch, > ZOOKEEPER-1426-2.patch, ZOOKEEPER-1426-3.patch > > > Add a version command to the zkServer.sh. > Hadoop does this by having a special main class: > org.apache.hadoop.util.VersionInfo > We could do something similar, hook it into our current version information > class (perhaps add main to that class). > Would also need to add a new "version" command to zkServer.sh that calls this. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (ZOOKEEPER-1426) add version command to the zookeeper server
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13430713#comment-13430713 ] Jakob Homan commented on ZOOKEEPER-1426: Hey Eli. Looks like the new patch picked up some changes from the changelog. Also, can you look into the [new findbugs warning|https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1154//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html]? Thanks. > add version command to the zookeeper server > --- > > Key: ZOOKEEPER-1426 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1426 > Project: ZooKeeper > Issue Type: Improvement > Components: scripts, server >Affects Versions: 3.3.5 >Reporter: Patrick Hunt >Assignee: Eli Reisman > Labels: newbie, patch > Attachments: MAPREDUCE-4282-2.patch, ZOOKEEPER-1426-1.patch, > ZOOKEEPER-1426-2.patch > > > Add a version command to the zkServer.sh. > Hadoop does this by having a special main class: > org.apache.hadoop.util.VersionInfo > We could do something similar, hook it into our current version information > class (perhaps add main to that class). > Would also need to add a new "version" command to zkServer.sh that calls this. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (ZOOKEEPER-1520) A txn log record with a corrupt sentinel byte looks like EOF
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Bridge updated ZOOKEEPER-1520: --- Attachment: init.out > A txn log record with a corrupt sentinel byte looks like EOF > > > Key: ZOOKEEPER-1520 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1520 > Project: ZooKeeper > Issue Type: Bug > Components: server >Affects Versions: 3.3.5 > Environment: all >Reporter: Bill Bridge >Priority: Minor > Labels: newbie > Attachments: ant.out, checkout.out, init.out, init.out > > Original Estimate: 24h > Remaining Estimate: 24h > > In Util.readTxnBytes() the sentinel is compared with 0x42 and if it does not > match then the record is considered partially written and thus the EOF. > However if it is a partial record the sentinel should be 0x00 since that is > what the log is initialized with. Any other value would indicate corruption > and should throw an IOException rather than indicate EOF. See > [ZOOKEEPER-1453|https://issues.apache.org/jira/browse/ZOOKEEPER-1453] for a > related issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (ZOOKEEPER-1520) A txn log record with a corrupt sentinel byte looks like EOF
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Bridge updated ZOOKEEPER-1520: --- Attachment: ant.out checkout.out > A txn log record with a corrupt sentinel byte looks like EOF > > > Key: ZOOKEEPER-1520 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1520 > Project: ZooKeeper > Issue Type: Bug > Components: server >Affects Versions: 3.3.5 > Environment: all >Reporter: Bill Bridge >Priority: Minor > Labels: newbie > Attachments: ant.out, checkout.out, init.out, init.out > > Original Estimate: 24h > Remaining Estimate: 24h > > In Util.readTxnBytes() the sentinel is compared with 0x42 and if it does not > match then the record is considered partially written and thus the EOF. > However if it is a partial record the sentinel should be 0x00 since that is > what the log is initialized with. Any other value would indicate corruption > and should throw an IOException rather than indicate EOF. See > [ZOOKEEPER-1453|https://issues.apache.org/jira/browse/ZOOKEEPER-1453] for a > related issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (ZOOKEEPER-1520) A txn log record with a corrupt sentinel byte looks like EOF
[
https://issues.apache.org/jira/browse/ZOOKEEPER-1520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13430693#comment-13430693
]
Bill Bridge commented on ZOOKEEPER-1520:
I have been unable to checkout the trunk and successfully run the tests. I am
using a Solaris 10 SPARC machine, and I expect that is part of my problem.
I eventually get the following error after "ant test" runs for 35 minutes:
{quote}
/zookeeper/zookeeper-trunk/build.xml:1240: Execute failed: java.io.IOException:
Cannot run program "autoreconf" (in directory
"/zookeeper/zookeeper-trunk/src/c"): error=2, No such file or directory
{quote}
Here are the commands I enter:
{quote}
bash-3.00$ rm -rf zookeeper-trunk/bash-3.00$ svn checkout
http://svn.apache.org/repos/asf/zookeeper/trunk/ zookeeper-trunk &>checkout.out
bash-3.00$ cd zookeeper-trunk/
bash-3.00$ ant init &>../init.out
bash-3.00$ ant test &>../ant.out
{quote}
I will attach the output files.
The autoreconf file is really missing. It seems to be related to compiling C
code to run natively, which is why I expect it is a SPARC problem.
Am I doing something wrong or is development on SPARC Solaris really broken?
I am very much a newbie to large scale Java development such as ZooKeeper. The
instructions on the how to contribute page were not sufficient for me. I had
previously downloaded zookeeper-3.3.5 and got it running under eclipse on
windows. I found out the hard way that the procedure for a checked out version
is quite different.
It would be nice to list the tools that should be installed such as ivy,
eclipse, ant, ... and where they can be found for download. It is particularly
important to specify which version of the JDK should be used since using a 1.7
feature in ZooKeeper would be bad if users are running a 1.6 JRE. I still do
not know which JDK is appropriate.
A bit more explaination about how the build file works, and what it is capable
of would be helpful. I have never used ant before so it took awhile to
understand build.xml. A list of the high level targets, their intended use, and
what they do would have told me that I did not need to find libraries like
log4j online. I had never heard of ivy. Understanding why I should do something
is better than just being told what to type.
> A txn log record with a corrupt sentinel byte looks like EOF
>
>
> Key: ZOOKEEPER-1520
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1520
> Project: ZooKeeper
> Issue Type: Bug
> Components: server
>Affects Versions: 3.3.5
> Environment: all
>Reporter: Bill Bridge
>Priority: Minor
> Labels: newbie
> Attachments: init.out
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> In Util.readTxnBytes() the sentinel is compared with 0x42 and if it does not
> match then the record is considered partially written and thus the EOF.
> However if it is a partial record the sentinel should be 0x00 since that is
> what the log is initialized with. Any other value would indicate corruption
> and should throw an IOException rather than indicate EOF. See
> [ZOOKEEPER-1453|https://issues.apache.org/jira/browse/ZOOKEEPER-1453] for a
> related issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (ZOOKEEPER-1520) A txn log record with a corrupt sentinel byte looks like EOF
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Bridge updated ZOOKEEPER-1520: --- Attachment: init.out > A txn log record with a corrupt sentinel byte looks like EOF > > > Key: ZOOKEEPER-1520 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1520 > Project: ZooKeeper > Issue Type: Bug > Components: server >Affects Versions: 3.3.5 > Environment: all >Reporter: Bill Bridge >Priority: Minor > Labels: newbie > Attachments: init.out > > Original Estimate: 24h > Remaining Estimate: 24h > > In Util.readTxnBytes() the sentinel is compared with 0x42 and if it does not > match then the record is considered partially written and thus the EOF. > However if it is a partial record the sentinel should be 0x00 since that is > what the log is initialized with. Any other value would indicate corruption > and should throw an IOException rather than indicate EOF. See > [ZOOKEEPER-1453|https://issues.apache.org/jira/browse/ZOOKEEPER-1453] for a > related issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (ZOOKEEPER-1178) Add eclipse target for supporting Apache IvyDE
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13430670#comment-13430670 ] Warren Turkal commented on ZOOKEEPER-1178: -- Is there anything else that needs to be done before this can be submitted? > Add eclipse target for supporting Apache IvyDE > -- > > Key: ZOOKEEPER-1178 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1178 > Project: ZooKeeper > Issue Type: Improvement > Components: build > Environment: Mac OS X w/ Eclipse 3.7. However, I believe this will > work in any Eclipse environment. >Reporter: Warren Turkal >Assignee: Warren Turkal >Priority: Minor > Fix For: 3.5.0 > > Attachments: ZOOKEEPER-1178.patch > > Original Estimate: 1h > Remaining Estimate: 1h > > This patch adds support for Eclipse with Apache IvyDE, which is the extension > that integrates Ivy support into Eclipse. This allows the creation of what > appear to be fully portable .eclipse and .classpath files. I will be posting > a patch shortly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (ZOOKEEPER-1525) Plumb ZooKeeperServer object into auth plugins
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13430665#comment-13430665 ] Warren Turkal commented on ZOOKEEPER-1525: -- This still doesn't appear to have triggered a jenkins build. What's wrong? > Plumb ZooKeeperServer object into auth plugins > -- > > Key: ZOOKEEPER-1525 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1525 > Project: ZooKeeper > Issue Type: Improvement >Reporter: Warren Turkal > Attachments: ZOOKEEPER-1525.patch > > > I want to plumb the ZooKeeperServer object into the auth plugins so that I > can store authentication data in zookeeper itself. With access to the > ZooKeeperServer object, I also have access to the ZKDatabase and can look up > entries in the local copy of the zookeeper data. > In order to implement this, I make sure that a ZooKeeperServer instance is > passed in to the ProviderRegistry.initialize() method. Then initialize() will > try to find a constructor for the AuthenticationProvider that takes a > ZooKeeperServer instance. If the constructor is found, it will be used. > Otherwise, initialize() will look for a constructor that takes no arguments > and use that instead. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (BOOKKEEPER-191) Hub server should change ledger to write, so consumed messages have chance to be garbage collected.
[
https://issues.apache.org/jira/browse/BOOKKEEPER-191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13430409#comment-13430409
]
Ivan Kelly commented on BOOKKEEPER-191:
---
{quote}
ChangeLedgerOp is asynchronous op, but PersisteOp is synchronous op. so when
the ChangeLedgerOp is executing, the previous persist ops might be still
on-the-fly. so doChangeLedger is to avoid close ledger until all previous
requests are finished. then it is safe to change ledger.
{quote}
As I understand it, thats not how TopicOpQueuer works. Only one op is allows to
run for a topic at a time whether it's sync or async. When an op is pushed onto
the TopicOpQueue, the op is first put on the work queue for that topic, and
then run if it is the only thing in the queue. If it is not the only thing in
the queue it will wait. Then it will be run when another op(sync or async)
finishes and runs popAndRunNext().
> Hub server should change ledger to write, so consumed messages have chance to
> be garbage collected.
> ---
>
> Key: BOOKKEEPER-191
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-191
> Project: Bookkeeper
> Issue Type: Improvement
>Affects Versions: 4.1.0
>Reporter: Sijie Guo
>Assignee: Sijie Guo
> Fix For: 4.2.0
>
> Attachments: BK-191.diff, BOOKKEEPER-191.diff, BOOKKEEPER-191.diff
>
>
> currently, hub server write entries to only one ledger, if a topic doesn't
> change ownership, all entries will be added to this ledger. so those consumed
> messages don't have chance to be garbage collected.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (ZOOKEEPER-1525) Plumb ZooKeeperServer object into auth plugins
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Warren Turkal updated ZOOKEEPER-1525: - Attachment: (was: ZOOKEEPER-1525.patch) > Plumb ZooKeeperServer object into auth plugins > -- > > Key: ZOOKEEPER-1525 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1525 > Project: ZooKeeper > Issue Type: Improvement >Reporter: Warren Turkal > Attachments: ZOOKEEPER-1525.patch > > > I want to plumb the ZooKeeperServer object into the auth plugins so that I > can store authentication data in zookeeper itself. With access to the > ZooKeeperServer object, I also have access to the ZKDatabase and can look up > entries in the local copy of the zookeeper data. > In order to implement this, I make sure that a ZooKeeperServer instance is > passed in to the ProviderRegistry.initialize() method. Then initialize() will > try to find a constructor for the AuthenticationProvider that takes a > ZooKeeperServer instance. If the constructor is found, it will be used. > Otherwise, initialize() will look for a constructor that takes no arguments > and use that instead. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (ZOOKEEPER-1525) Plumb ZooKeeperServer object into auth plugins
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Warren Turkal updated ZOOKEEPER-1525: - Attachment: (was: ZOOKEEPER-1525.patch) > Plumb ZooKeeperServer object into auth plugins > -- > > Key: ZOOKEEPER-1525 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1525 > Project: ZooKeeper > Issue Type: Improvement >Reporter: Warren Turkal > Attachments: ZOOKEEPER-1525.patch > > > I want to plumb the ZooKeeperServer object into the auth plugins so that I > can store authentication data in zookeeper itself. With access to the > ZooKeeperServer object, I also have access to the ZKDatabase and can look up > entries in the local copy of the zookeeper data. > In order to implement this, I make sure that a ZooKeeperServer instance is > passed in to the ProviderRegistry.initialize() method. Then initialize() will > try to find a constructor for the AuthenticationProvider that takes a > ZooKeeperServer instance. If the constructor is found, it will be used. > Otherwise, initialize() will look for a constructor that takes no arguments > and use that instead. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (ZOOKEEPER-1525) Plumb ZooKeeperServer object into auth plugins
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Warren Turkal updated ZOOKEEPER-1525: - Attachment: ZOOKEEPER-1525.patch updated patch > Plumb ZooKeeperServer object into auth plugins > -- > > Key: ZOOKEEPER-1525 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1525 > Project: ZooKeeper > Issue Type: Improvement >Reporter: Warren Turkal > Attachments: ZOOKEEPER-1525.patch > > > I want to plumb the ZooKeeperServer object into the auth plugins so that I > can store authentication data in zookeeper itself. With access to the > ZooKeeperServer object, I also have access to the ZKDatabase and can look up > entries in the local copy of the zookeeper data. > In order to implement this, I make sure that a ZooKeeperServer instance is > passed in to the ProviderRegistry.initialize() method. Then initialize() will > try to find a constructor for the AuthenticationProvider that takes a > ZooKeeperServer instance. If the constructor is found, it will be used. > Otherwise, initialize() will look for a constructor that takes no arguments > and use that instead. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
ZooKeeper_branch34_solaris - Build # 266 - Failure
See https://builds.apache.org/job/ZooKeeper_branch34_solaris/266/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 155000 lines...] [junit] 2012-08-07 08:00:28,207 [myid:] - INFO [main:JMXEnv@105] - expect:InMemoryDataTree [junit] 2012-08-07 08:00:28,208 [myid:] - INFO [main:JMXEnv@108] - found:InMemoryDataTree org.apache.ZooKeeperService:name0=StandaloneServer_port-1,name1=InMemoryDataTree [junit] 2012-08-07 08:00:28,209 [myid:] - INFO [main:JMXEnv@105] - expect:StandaloneServer_port [junit] 2012-08-07 08:00:28,209 [myid:] - INFO [main:JMXEnv@108] - found:StandaloneServer_port org.apache.ZooKeeperService:name0=StandaloneServer_port-1 [junit] 2012-08-07 08:00:28,210 [myid:] - INFO [main:ClientBase@421] - STOPPING server [junit] 2012-08-07 08:00:28,213 [myid:] - INFO [main:ZooKeeperServer@419] - shutting down [junit] 2012-08-07 08:00:28,214 [myid:] - INFO [main:SessionTrackerImpl@220] - Shutting down [junit] 2012-08-07 08:00:28,214 [myid:] - INFO [main:PrepRequestProcessor@743] - Shutting down [junit] 2012-08-07 08:00:28,215 [myid:] - INFO [main:SyncRequestProcessor@175] - Shutting down [junit] 2012-08-07 08:00:28,215 [myid:] - INFO [ProcessThread(sid:0 cport:-1)::PrepRequestProcessor@143] - PrepRequestProcessor exited loop! [junit] 2012-08-07 08:00:28,216 [myid:] - INFO [SyncThread:0:SyncRequestProcessor@155] - SyncRequestProcessor exited! [junit] 2012-08-07 08:00:28,217 [myid:] - INFO [main:FinalRequestProcessor@415] - shutdown of request processor complete [junit] 2012-08-07 08:00:28,219 [myid:] - INFO [main:FourLetterWordMain@43] - connecting to 127.0.0.1 11221 [junit] 2012-08-07 08:00:28,220 [myid:] - INFO [main:JMXEnv@133] - ensureOnly:[] [junit] 2012-08-07 08:00:28,221 [myid:] - INFO [main:ClientBase@414] - STARTING server [junit] 2012-08-07 08:00:28,222 [myid:] - INFO [main:ZooKeeperServer@162] - Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 6 datadir /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch34_solaris/trunk/build/test/tmp/test6871417963376620236.junit.dir/version-2 snapdir /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch34_solaris/trunk/build/test/tmp/test6871417963376620236.junit.dir/version-2 [junit] 2012-08-07 08:00:28,224 [myid:] - INFO [main:NIOServerCnxnFactory@108] - binding to port 0.0.0.0/0.0.0.0:11221 [junit] 2012-08-07 08:00:28,226 [myid:] - INFO [main:FileSnap@83] - Reading snapshot /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch34_solaris/trunk/build/test/tmp/test6871417963376620236.junit.dir/version-2/snapshot.b [junit] 2012-08-07 08:00:28,229 [myid:] - INFO [main:FileTxnSnapLog@240] - Snapshotting: 0xb to /zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch34_solaris/trunk/build/test/tmp/test6871417963376620236.junit.dir/version-2/snapshot.b [junit] 2012-08-07 08:00:28,232 [myid:] - INFO [main:FourLetterWordMain@43] - connecting to 127.0.0.1 11221 [junit] 2012-08-07 08:00:28,233 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@211] - Accepted socket connection from /127.0.0.1:49849 [junit] 2012-08-07 08:00:28,233 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxn@821] - Processing stat command from /127.0.0.1:49849 [junit] 2012-08-07 08:00:28,234 [myid:] - INFO [Thread-5:NIOServerCnxn$StatCommand@655] - Stat command output [junit] 2012-08-07 08:00:28,234 [myid:] - INFO [Thread-5:NIOServerCnxn@1001] - Closed socket connection for client /127.0.0.1:49849 (no session established for client) [junit] 2012-08-07 08:00:28,235 [myid:] - INFO [main:JMXEnv@133] - ensureOnly:[InMemoryDataTree, StandaloneServer_port] [junit] 2012-08-07 08:00:28,237 [myid:] - INFO [main:JMXEnv@105] - expect:InMemoryDataTree [junit] 2012-08-07 08:00:28,238 [myid:] - INFO [main:JMXEnv@108] - found:InMemoryDataTree org.apache.ZooKeeperService:name0=StandaloneServer_port-1,name1=InMemoryDataTree [junit] 2012-08-07 08:00:28,238 [myid:] - INFO [main:JMXEnv@105] - expect:StandaloneServer_port [junit] 2012-08-07 08:00:28,239 [myid:] - INFO [main:JMXEnv@108] - found:StandaloneServer_port org.apache.ZooKeeperService:name0=StandaloneServer_port-1 [junit] 2012-08-07 08:00:28,240 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@57] - FINISHED TEST METHOD testQuota [junit] 2012-08-07 08:00:28,240 [myid:] - INFO [main:ClientBase@451] - tearDown starting [junit] 2012-08-07 08:00:28,652 [myid:] - INFO [main:ZooKeeper@679] - Session: 0x13900196259 closed [junit] 2012-08-07 08:00:28,653 [myid:] - INFO [main:ClientBase@421] - STOPPING server [junit] 2012-08-07 08:00
[jira] [Commented] (ZOOKEEPER-1525) Plumb ZooKeeperServer object into auth plugins
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13430080#comment-13430080 ] Warren Turkal commented on ZOOKEEPER-1525: -- I am working on making the change to the patch now. However, would it be possible to make the jenkins job accept git patches as is so that folks using the apache git won't have to remember to adopt a special setting to submit patches? For example, could the job try -p1 if -p0 fails when patching in the diff? > Plumb ZooKeeperServer object into auth plugins > -- > > Key: ZOOKEEPER-1525 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1525 > Project: ZooKeeper > Issue Type: Improvement >Reporter: Warren Turkal > Attachments: ZOOKEEPER-1525.patch, ZOOKEEPER-1525.patch > > > I want to plumb the ZooKeeperServer object into the auth plugins so that I > can store authentication data in zookeeper itself. With access to the > ZooKeeperServer object, I also have access to the ZKDatabase and can look up > entries in the local copy of the zookeeper data. > In order to implement this, I make sure that a ZooKeeperServer instance is > passed in to the ProviderRegistry.initialize() method. Then initialize() will > try to find a constructor for the AuthenticationProvider that takes a > ZooKeeperServer instance. If the constructor is found, it will be used. > Otherwise, initialize() will look for a constructor that takes no arguments > and use that instead. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
