[jira] Updated: (ZOOKEEPER-214) add new "stat reset" command to server admin port
[ https://issues.apache.org/jira/browse/ZOOKEEPER-214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-214: --- Status: Patch Available (was: Open) > add new "stat reset" command to server admin port > - > > Key: ZOOKEEPER-214 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-214 > Project: Zookeeper > Issue Type: Improvement > Components: server >Reporter: Patrick Hunt >Assignee: Patrick Hunt > Fix For: 3.1.0 > > Attachments: ZOOKEEPER-214.patch > > > A new command should be added to the server admin port (client port) that > allows users to reset the stats. > We saw cases during troubleshooting where we would have liked to reset the > "min/avg/max latency" stats, but were unable to do so (short of restarting > the server). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-214) add new "stat reset" command to server admin port
[ https://issues.apache.org/jira/browse/ZOOKEEPER-214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-214: --- Attachment: ZOOKEEPER-214.patch Added 'srst' or "stat reset" command to the list of 4 letter words supported by the command port. > add new "stat reset" command to server admin port > - > > Key: ZOOKEEPER-214 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-214 > Project: Zookeeper > Issue Type: Improvement > Components: server >Reporter: Patrick Hunt > Fix For: 3.1.0 > > Attachments: ZOOKEEPER-214.patch > > > A new command should be added to the server admin port (client port) that > allows users to reset the stats. > We saw cases during troubleshooting where we would have liked to reset the > "min/avg/max latency" stats, but were unable to do so (short of restarting > the server). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (ZOOKEEPER-214) add new "stat reset" command to server admin port
[ https://issues.apache.org/jira/browse/ZOOKEEPER-214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt reassigned ZOOKEEPER-214: -- Assignee: Patrick Hunt > add new "stat reset" command to server admin port > - > > Key: ZOOKEEPER-214 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-214 > Project: Zookeeper > Issue Type: Improvement > Components: server >Reporter: Patrick Hunt >Assignee: Patrick Hunt > Fix For: 3.1.0 > > Attachments: ZOOKEEPER-214.patch > > > A new command should be added to the server admin port (client port) that > allows users to reset the stats. > We saw cases during troubleshooting where we would have liked to reset the > "min/avg/max latency" stats, but were unable to do so (short of restarting > the server). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (ZOOKEEPER-252) PurgeTxnLog is not handling the new dataDir directory structure
PurgeTxnLog is not handling the new dataDir directory structure --- Key: ZOOKEEPER-252 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-252 Project: Zookeeper Issue Type: Bug Components: server Affects Versions: 3.0.1, 3.0.0 Reporter: Patrick Hunt Assignee: Mahadev konar Priority: Critical Fix For: 3.1.0 org.apache.zookeeper.server.PurgeTxnLog class has not been updated to handle the new directory structure imposed by the upgrade from v2 to v3 of ZooKeeper. In particular the dataDir now has a "version-2" subdirectory that stores all of the snaps/transactionallogs for version2 of the persistence layer. I also note that the documentation of this class is particularly poor. I'm working on ZOOKEEPER-229 and would like to point to the API docs for this class regarding usage but they api docs are nonexistent Also - I think it's important for the user to be able to specify the number of "backup" snaps and logs that should be kept -- right now it seems we delete all but the current snaps/txlogs. Either by count or by date -- ie "remove anything 5 days or older, with a minum of 3 most recents snaps (and accompanying txlogs)" seems like a pretty common user case (assuming the operator is doing system backups every X days, etc...) in general this class needs some tlc - the formatting should also be cleaned up. Also - the API docs for this and LogFormatter are not included in the build.xml "javadoc" target. These are user utilities so javadoc for these two classes should be included. I will fix this issue as part of ZOOKEEPER-229. I'm also updateing the forrest documention in 229 so don't worry about that either. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-251) NullPointerException stopping and starting Zookeeper servers
[
https://issues.apache.org/jira/browse/ZOOKEEPER-251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Hunt updated ZOOKEEPER-251:
---
Resolution: Fixed
Hadoop Flags: [Reviewed]
Status: Resolved (was: Patch Available)
+1 - looks good, tests pass.
Committed revision 725454.
> NullPointerException stopping and starting Zookeeper servers
>
>
> Key: ZOOKEEPER-251
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-251
> Project: Zookeeper
> Issue Type: Bug
> Components: server
>Affects Versions: 3.0.0, 3.0.1
> Environment: Tested with JDK 1.5, Solaris, but I suspect it is not
> relevant in this case.
>Reporter: Thomas Vinod Johnson
>Assignee: Mahadev konar
>Priority: Blocker
> Fix For: 3.1.0
>
> Attachments: ZOOKEEPER-251.patch, ZOOKEEPER-251.patch
>
>
> See the following thread for the original report:
> http://mail-archives.apache.org/mod_mbox/hadoop-zookeeper-user/200812.mbox/browser
> Steps to reproduce:
> 1) Start a replicated zookeeper service consisting of 3 zookeeper (3.0.1)
> servers all running on the same host (of course, all using their own ports
> and log directories)
> 2) Create one znode in this ensemble (using the zookeeper client console, I
> issued 'create /node1 node1data').
> 3) Stop, then restart a single zookeeper server; moving onto the next one a
> few seconds later.
> 4) Go back to 3. After 4-5 iterations, the following should occur, with the
> failing server exiting:
> java.lang.NullPointerException
> at
> org.apache.zookeeper.server.persistence.FileTxnLog$FileTxnIterator.next(FileTxnLog.java:447)
> at
> org.apache.zookeeper.server.persistence.FileTxnLog$FileTxnIterator.init(FileTxnLog.java:358)
> at
> org.apache.zookeeper.server.persistence.FileTxnLog$FileTxnIterator.(FileTxnLog.java:333)
> at
> org.apache.zookeeper.server.persistence.FileTxnLog.read(FileTxnLog.java:250)
> at
> org.apache.zookeeper.server.persistence.FileTxnSnapLog.restore(FileTxnSnapLog.java:102)
> at
> org.apache.zookeeper.server.ZooKeeperServer.loadData(ZooKeeperServer.java:183)
> at org.apache.zookeeper.server.quorum.Leader.lead(Leader.java:245)
> at
> org.apache.zookeeper.server.quorum.QuorumPeer.run(QuorumPeer.java:421)
> 2008-12-08 14:14:24,880 - INFO
> [QuorumPeer:/0:0:0:0:0:0:0:0:2183:[EMAIL PROTECTED] - Shutdown called
> java.lang.Exception: shutdown Leader! reason: Forcing shutdown
> at
> org.apache.zookeeper.server.quorum.Leader.shutdown(Leader.java:336)
> at
> org.apache.zookeeper.server.quorum.QuorumPeer.run(QuorumPeer.java:427)
> Exception in thread "QuorumPeer:/0:0:0:0:0:0:0:0:2183"
> java.lang.NullPointerException
> at
> org.apache.zookeeper.server.quorum.Leader.shutdown(Leader.java:339)
> at
> org.apache.zookeeper.server.quorum.QuorumPeer.run(QuorumPeer.java:427)
> The inputStream field is null, apparently because next is being called
> at line 358 even after next returns false. Having very little knowledge
> about the implementation, I don't know if the existence of hdr.getZxid()
> >= zxid is supposed to be an invariant across all invocations of the
> server; however the following change to FileTxnLog.java seems to make
> the problem go away.
> diff FileTxnLog.java /tmp/FileTxnLog.java
> 358c358,359
> < next();
> ---
> > if (!next())
> > return;
> 447c448,450
> < inputStream.close();
> ---
> > if (inputStream != null) {
> > inputStream.close();
> > }
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-250) isvalidsnapshot should handle the case of 0 snapshot files better.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-250: --- Status: Open (was: Patch Available) I'd like to see a test for this one. > isvalidsnapshot should handle the case of 0 snapshot files better. > -- > > Key: ZOOKEEPER-250 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-250 > Project: Zookeeper > Issue Type: Bug >Affects Versions: 3.0.1, 3.0.0 >Reporter: Mahadev konar >Assignee: Mahadev konar > Fix For: 3.1.0 > > Attachments: ZOOKEEPER-250.patch > > > the isvalidsnapshot will fail with negative seek if 0 snapshot files exist. > We should just return false in case the size of the snapshot is less than 5 > bytes. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-225) c client should log an info message in zookeeper_init detailing connection parameters
[ https://issues.apache.org/jira/browse/ZOOKEEPER-225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12655355#action_12655355 ] Mahadev konar commented on ZOOKEEPER-225: - +1 for the patch... its good that you didnt print the passwd :) ... > c client should log an info message in zookeeper_init detailing connection > parameters > - > > Key: ZOOKEEPER-225 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-225 > Project: Zookeeper > Issue Type: Improvement > Components: c client >Affects Versions: 3.0.0, 3.0.1 >Reporter: Patrick Hunt >Assignee: Patrick Hunt >Priority: Minor > Fix For: 3.1.0 > > Attachments: ZOOKEEPER-225.patch > > > I've debugged a few situations where the client connection param was not set > properly (even though the user swore that it was). We should log info level > message during init to enable us (and user) to easier debug. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-225) c client should log an info message in zookeeper_init detailing connection parameters
[ https://issues.apache.org/jira/browse/ZOOKEEPER-225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-225: --- Assignee: Patrick Hunt Affects Version/s: 3.0.1 Status: Patch Available (was: Open) > c client should log an info message in zookeeper_init detailing connection > parameters > - > > Key: ZOOKEEPER-225 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-225 > Project: Zookeeper > Issue Type: Improvement > Components: c client >Affects Versions: 3.0.1, 3.0.0 >Reporter: Patrick Hunt >Assignee: Patrick Hunt >Priority: Minor > Fix For: 3.1.0 > > Attachments: ZOOKEEPER-225.patch > > > I've debugged a few situations where the client connection param was not set > properly (even though the user swore that it was). We should log info level > message during init to enable us (and user) to easier debug. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-225) c client should log an info message in zookeeper_init detailing connection parameters
[ https://issues.apache.org/jira/browse/ZOOKEEPER-225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-225: --- Attachment: ZOOKEEPER-225.patch This patch adds info logs to both the c and java clients detailing the connection parameters - useful in certain debugging situations. > c client should log an info message in zookeeper_init detailing connection > parameters > - > > Key: ZOOKEEPER-225 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-225 > Project: Zookeeper > Issue Type: Improvement > Components: c client >Affects Versions: 3.0.0, 3.0.1 >Reporter: Patrick Hunt >Priority: Minor > Fix For: 3.1.0 > > Attachments: ZOOKEEPER-225.patch > > > I've debugged a few situations where the client connection param was not set > properly (even though the user swore that it was). We should log info level > message during init to enable us (and user) to easier debug. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-16) Need to do path validation
[ https://issues.apache.org/jira/browse/ZOOKEEPER-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-16: -- Affects Version/s: 3.0.0 3.0.1 Status: Patch Available (was: Open) > Need to do path validation > -- > > Key: ZOOKEEPER-16 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-16 > Project: Zookeeper > Issue Type: Bug > Components: c client, java client, server >Affects Versions: 3.0.1, 3.0.0 >Reporter: Patrick Hunt >Assignee: Patrick Hunt > Fix For: 3.1.0 > > Attachments: ZOOKEEPER-16.patch, ZOOKEEPER-16.patch > > > Moved from SourceForge to Apache. > http://sourceforge.net/tracker/index.php?func=detail&aid=1963141&group_id=209147&atid=1008544 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-16) Need to do path validation
[ https://issues.apache.org/jira/browse/ZOOKEEPER-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-16: -- Attachment: ZOOKEEPER-16.patch Updated patch based on comment/feedback. We now throw IllegalArgumentException in the java client if the path is not valid In the c client we return a rc of ZBADARGUMENT (c client was already checking for null - just added the addl conditions) Tests added to both c and java. Note: valid path definition already existed in the programmer guide, no additional doc changes were necessary -- although I did update the java and c client API docs as appropriate. > Need to do path validation > -- > > Key: ZOOKEEPER-16 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-16 > Project: Zookeeper > Issue Type: Bug > Components: c client, java client, server >Affects Versions: 3.0.0, 3.0.1 >Reporter: Patrick Hunt >Assignee: Patrick Hunt > Fix For: 3.1.0 > > Attachments: ZOOKEEPER-16.patch, ZOOKEEPER-16.patch > > > Moved from SourceForge to Apache. > http://sourceforge.net/tracker/index.php?func=detail&aid=1963141&group_id=209147&atid=1008544 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-230) Improvements to FLE
[
https://issues.apache.org/jira/browse/ZOOKEEPER-230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12655312#action_12655312
]
Mahadev konar commented on ZOOKEEPER-230:
-
the patch looks good except for a few nits:
- this is just a documentation bug
{noformat}
+* notification checks. This impacts the amount of time to get
+* the system up again after long partitions. Currently 6 seconds.
*/
{noformat}
this should be 60 seconds.
- the other one is
{noformat}
-
+LOG.info("About to leave instance:" +
proposedLeader + ", " + proposedZxid + ", " + self.getId() + ", " +
self.getPeerState());
{noformat}
we should wrap these lines around to confirm to 80 character columns. We dont
have to be pedantic about the column length but 80-90 column is good enough i
think. Their are a few more lines I think that are overly long and should be
wrapped arnd.
> Improvements to FLE
> ---
>
> Key: ZOOKEEPER-230
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-230
> Project: Zookeeper
> Issue Type: Improvement
> Components: leaderElection
>Affects Versions: 3.0.0
>Reporter: Flavio Paiva Junqueira
>Assignee: Flavio Paiva Junqueira
> Fix For: 3.1.0
>
> Attachments: ZOOKEEPER-230.patch, ZOOKEEPER-230.patch,
> ZOOKEEPER-230.patch, ZOOKEEPER-230.patch
>
>
> I'm about to attach a patch that implements the following modifications:
> . Currently, if a server is on leader election and doesn't receive a
> notification for some amount of time t, then it sends a new set of
> notifications if at least one server has delivered a message from the
> previous set. With this patch, the amount of time a server waits for a
> notification before sending a new set increases exponentially;
> . I have separated connecting to servers and queuing new notification
> messages. Before they were all in the same message. The advantage is that now
> I can tell to an instance of QuorumCnxManager to try to connect to other
> servers without generating new notification messages;
> . I have changed the logging level of several messages on QuorumCnxManager.
> They were "warn", but they should really be either "info" or "debug". I've
> changed them to info.
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-241) Build of a distro fails after clean target is run
[
https://issues.apache.org/jira/browse/ZOOKEEPER-241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12655209#action_12655209
]
Hudson commented on ZOOKEEPER-241:
--
Integrated in ZooKeeper-trunk #168 (See
[http://hudson.zones.apache.org/hudson/job/ZooKeeper-trunk/168/])
. Build of a distro fails after clean target is run. (patrick hunt via
mahadev)
> Build of a distro fails after clean target is run
> -
>
> Key: ZOOKEEPER-241
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-241
> Project: Zookeeper
> Issue Type: Bug
> Components: build
>Affects Versions: 3.0.0, 3.0.1
>Reporter: Nigel Daley
>Assignee: Patrick Hunt
>Priority: Critical
> Fix For: 3.1.0
>
> Attachments: ZOOKEEPER-241.patch
>
>
> When the ZooKeeper distro is downloaded, if the clean target is run, it
> deletes the .revision file:
> {quote}
> clean:
> [delete] Deleting directory /home/foo/zookeeper-3.0.1/build
> [delete] Deleting directory /home/foo/zookeeper-3.0.1/src/java/generated
> [delete] Deleting directory /home/foo/zookeeper-3.0.1/src/c/generated
> [delete] Deleting directory /home/foo/zookeeper-3.0.1/.revision
> {quote}
> This causes subsequent builds in the distro to fail with:
> {quote}
> compile-main:
>[javac] Compiling 73 source files to
> /home/foo/zookeeper-3.0.1/build/classes
>[javac]
> /home/foo/zookeeper-3.0.1/src/java/main/org/apache/zookeeper/Version.java:21:
> package org.apache.zookeeper.version does not exist
>[javac] public class Version implements org.apache.zookeeper.version.Info{
>[javac] ^
>...
> {quote}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-249) QuorumPeer.getClientPort() always returns -1
[ https://issues.apache.org/jira/browse/ZOOKEEPER-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12655214#action_12655214 ] Hudson commented on ZOOKEEPER-249: -- Integrated in ZooKeeper-trunk #168 (See [http://hudson.zones.apache.org/hudson/job/ZooKeeper-trunk/168/]) > QuorumPeer.getClientPort() always returns -1 > > > Key: ZOOKEEPER-249 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-249 > Project: Zookeeper > Issue Type: Bug >Affects Versions: 3.0.0, 3.0.1 >Reporter: Nitay Joffe >Assignee: Nitay Joffe >Priority: Trivial > Fix For: 3.1.0 > > Attachments: 249.patch > > > This was changed in SVN 700690: > http://svn.apache.org/viewvc/hadoop/zookeeper/trunk/src/java/main/org/apache/zookeeper/server/quorum/QuorumPeer.java?r1=700690&r2=700689&pathrev=700690 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-247) fix formatting of C API in ACL section of programmer guide
[ https://issues.apache.org/jira/browse/ZOOKEEPER-247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12655213#action_12655213 ] Hudson commented on ZOOKEEPER-247: -- Integrated in ZooKeeper-trunk #168 (See [http://hudson.zones.apache.org/hudson/job/ZooKeeper-trunk/168/]) . fix formatting of C API in ACL section of programmer guide. (patrick hunt via mahadev) > fix formatting of C API in ACL section of programmer guide > -- > > Key: ZOOKEEPER-247 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-247 > Project: Zookeeper > Issue Type: Bug > Components: documentation >Affects Versions: 3.0.0, 3.0.1 >Reporter: Patrick Hunt >Assignee: Patrick Hunt > Fix For: 3.1.0 > > Attachments: ZOOKEEPER-247.patch, ZOOKEEPER-247.patch, > ZOOKEEPER-247.patch > > > formatting of C api is wrong in acl section of prog guide -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-161) Content needed: "Designing a ZooKeeper Deployment"
[ https://issues.apache.org/jira/browse/ZOOKEEPER-161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12655208#action_12655208 ] Hudson commented on ZOOKEEPER-161: -- Integrated in ZooKeeper-trunk #168 (See [http://hudson.zones.apache.org/hudson/job/ZooKeeper-trunk/168/]) . Content needed: "Designing a ZooKeeper Deployment" > Content needed: "Designing a ZooKeeper Deployment" > -- > > Key: ZOOKEEPER-161 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-161 > Project: Zookeeper > Issue Type: Sub-task > Components: documentation >Affects Versions: 3.0.1 >Reporter: Robbie Scott >Assignee: Benjamin Reed > Fix For: 3.1.0 > > Attachments: ZOOKEEPER-161.patch, ZOOKEEPER-161.patch > > Original Estimate: 8h > Remaining Estimate: 8h > > We should document how ops engineer should design their ZooKeeper > deployments. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-245) update readme/quickstart to be release tar, rather than source, based
[ https://issues.apache.org/jira/browse/ZOOKEEPER-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12655211#action_12655211 ] Hudson commented on ZOOKEEPER-245: -- Integrated in ZooKeeper-trunk #168 (See [http://hudson.zones.apache.org/hudson/job/ZooKeeper-trunk/168/]) . update readme/quickstart to be release tar, rather than source, based (patrick hunt via mahadev) > update readme/quickstart to be release tar, rather than source, based > - > > Key: ZOOKEEPER-245 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-245 > Project: Zookeeper > Issue Type: Bug > Components: documentation >Affects Versions: 3.0.1 >Reporter: Patrick Hunt >Assignee: Patrick Hunt > Fix For: 3.1.0 > > Attachments: ZOOKEEPER-245.patch > > > Owen O'Malley mentioned: > - > we need to change both the README and quick start to assume you are working > with a release instead of a source tarball. Apache releases are the approved > way of getting the project. Documentation that assumes they are getting > source themselves doesn't reflect that. > - -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-243) add SEQUENCE flag documentation to the programming guide
[ https://issues.apache.org/jira/browse/ZOOKEEPER-243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12655210#action_12655210 ] Hudson commented on ZOOKEEPER-243: -- Integrated in ZooKeeper-trunk #168 (See [http://hudson.zones.apache.org/hudson/job/ZooKeeper-trunk/168/]) . add SEQUENCE flag documentation to the programming guide. (patrick hunt via mahadev) > add SEQUENCE flag documentation to the programming guide > > > Key: ZOOKEEPER-243 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-243 > Project: Zookeeper > Issue Type: Improvement > Components: documentation >Affects Versions: 3.0.0, 3.0.1 >Reporter: Patrick Hunt >Assignee: Patrick Hunt >Priority: Minor > Fix For: 3.1.0 > > Attachments: ZOOKEEPER-243.patch > > > There doesn't seem to be any docs in forrest detailing the sequence flag for > node creation. > In particular we should detail how the flag works, the naming format, and > also rollover (when does the number roll over to 0 again). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-248) QuorumPeer should use Map interface instead of HashMap implementation.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12655212#action_12655212 ] Hudson commented on ZOOKEEPER-248: -- Integrated in ZooKeeper-trunk #168 (See [http://hudson.zones.apache.org/hudson/job/ZooKeeper-trunk/168/]) > QuorumPeer should use Map interface instead of HashMap implementation. > -- > > Key: ZOOKEEPER-248 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-248 > Project: Zookeeper > Issue Type: Improvement > Components: quorum >Affects Versions: 3.0.0, 3.0.1 >Reporter: Nitay Joffe >Assignee: Nitay Joffe >Priority: Trivial > Fix For: 3.1.0 > > Attachments: 248.patch > > > Using HashMap directly to store quorumPeers member variable unnecessarily > decides for the user what implementation of Map to use. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Hudson build is back to normal: ZooKeeper-trunk #168
See http://hudson.zones.apache.org/hudson/job/ZooKeeper-trunk/168/changes
