Build failed in Hudson: ZooKeeper-trunk #93
See http://hudson.zones.apache.org/hudson/job/ZooKeeper-trunk/93/changes -- [...truncated 33461 lines...] [junit] 2008-09-24 10:58:33,953 - INFO [main:[EMAIL PROTECTED] - Session: 0x11c9402a67b closed [junit] 2008-09-24 10:58:33,953 - INFO [main-EventThread:[EMAIL PROTECTED] - EventThread shut down [junit] 2008-09-24 10:58:33,954 - INFO [main-SendThread:[EMAIL PROTECTED] - Attempting connection to server /127.0.0.1:33299 [junit] 2008-09-24 10:58:33,955 - INFO [main-SendThread:[EMAIL PROTECTED] - Priming connection to java.nio.channels.SocketChannel[connected local=/127.0.0.1:56549 remote=/127.0.0.1:33299] [junit] 2008-09-24 10:58:33,956 - WARN [NIOServerCxn.Factory:[EMAIL PROTECTED] - Connected to /127.0.0.1:56549 lastZxid 0 [junit] 2008-09-24 10:58:33,956 - WARN [NIOServerCxn.Factory:[EMAIL PROTECTED] - Creating new session 0x11c9402a67b0001 [junit] 2008-09-24 10:58:33,966 - WARN [SyncThread:[EMAIL PROTECTED] - Finished init of 0x11c9402a67b0001: true [junit] 2008-09-24 10:58:33,969 - INFO [main:[EMAIL PROTECTED] - before close zk with session id 0x11c9402a67b0001! [junit] 2008-09-24 10:58:33,969 - INFO [main:[EMAIL PROTECTED] - Closing session: 0x11c9402a67b0001 [junit] 2008-09-24 10:58:33,970 - INFO [main:[EMAIL PROTECTED] - Closing ClientCnxn for session: 0x11c9402a67b0001 [junit] 2008-09-24 10:58:33,971 - INFO [ProcessThread:[EMAIL PROTECTED] - Processed session termination request for id: 0x11c9402a67b0001 [junit] 2008-09-24 10:58:33,981 - INFO [main-SendThread:[EMAIL PROTECTED] - Exception while closing send thread for session 0x11c9402a67b0001 : Read error rc = -1 java.nio.DirectByteBuffer[pos=0 lim=4 cap=4] [junit] 2008-09-24 10:58:34,091 - INFO [main:[EMAIL PROTECTED] - Disconnecting ClientCnxn for session: 0x11c9402a67b0001 [junit] 2008-09-24 10:58:34,091 - INFO [main:[EMAIL PROTECTED] - Session: 0x11c9402a67b0001 closed [junit] 2008-09-24 10:58:34,092 - INFO [main-EventThread:[EMAIL PROTECTED] - EventThread shut down [junit] 2008-09-24 10:58:34,094 - ERROR [NIOServerCxn.Factory:[EMAIL PROTECTED] - => Goodbye cruel world <== [junit] 2008-09-24 10:58:34,094 - INFO [main:[EMAIL PROTECTED] - shutdown of request processor complete [junit] 2008-09-24 10:58:34,095 - INFO [main:[EMAIL PROTECTED] - FINISHED testSession [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.506 sec [junit] Running org.apache.zookeeper.test.SyncCallTest [junit] 2008-09-24 10:58:34,646 - INFO [main:[EMAIL PROTECTED] - STARTING testSync [junit] 2008-09-24 10:58:34,663 - INFO [main:[EMAIL PROTECTED] - Created server with dataDir:/zonestorage/hudson/home/hudson/hudson/jobs/ZooKeeper-trunk/workspace/trunk/build/test/tmp/test6541.junit.dir dataLogDir:/zonestorage/hudson/home/hudson/hudson/jobs/ZooKeeper-trunk/workspace/trunk/build/test/tmp/test6541.junit.dir tickTime:3000 [junit] 2008-09-24 10:58:34,721 - INFO [main:[EMAIL PROTECTED] - Client test setup finished [junit] 2008-09-24 10:58:34,723 - INFO [main:[EMAIL PROTECTED] - Starting ZK:Wed Sep 24 10:58:34 UTC 2008 [junit] 2008-09-24 10:58:34,734 - INFO [main-SendThread:[EMAIL PROTECTED] - Attempting connection to server /127.0.0.1:33221 [junit] 2008-09-24 10:58:34,735 - INFO [main-SendThread:[EMAIL PROTECTED] - Priming connection to java.nio.channels.SocketChannel[connected local=/127.0.0.1:56554 remote=/127.0.0.1:33221] [junit] 2008-09-24 10:58:34,739 - WARN [NIOServerCxn.Factory:[EMAIL PROTECTED] - Connected to /127.0.0.1:56554 lastZxid 0 [junit] 2008-09-24 10:58:34,741 - WARN [NIOServerCxn.Factory:[EMAIL PROTECTED] - Creating new session 0x11c9402aa49 [junit] 2008-09-24 10:58:34,762 - WARN [SyncThread:[EMAIL PROTECTED] - Finished init of 0x11c9402aa49: true [junit] 2008-09-24 10:58:34,763 - INFO [main:[EMAIL PROTECTED] - Beginning test:Wed Sep 24 10:58:34 UTC 2008 [junit] 2008-09-24 10:58:34,789 - INFO [main:[EMAIL PROTECTED] - Submitted all operations:Wed Sep 24 10:58:34 UTC 2008 [junit] 2008-09-24 10:58:35,005 - INFO [main:[EMAIL PROTECTED] - tearDown starting [junit] 2008-09-24 10:58:35,015 - ERROR [NIOServerCxn.Factory:[EMAIL PROTECTED] - => Goodbye cruel world <== [junit] 2008-09-24 10:58:35,015 - INFO [main:[EMAIL PROTECTED] - shutdown of request processor complete [junit] 2008-09-24 10:58:35,082 - INFO [main:[EMAIL PROTECTED] - FINISHED testSync [junit] 2008-09-24 10:58:35,041 - WARN [main-SendThread:[EMAIL PROTECTED] - Exception closing session 0x11c9402aa49 [junit] java.io.IOException: Read error rc = -1 java.nio.DirectByteBuffer[pos=0 lim=4 cap=4] [junit] at org.apache.zookeeper.ClientCnxn$SendThread.doIO(ClientCnxn.java:510) [junit] at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:740) [junit] Tests run: 1, Failures: 0, Errors:
[jira] Updated: (ZOOKEEPER-137) client watcher objects can lose events
[ https://issues.apache.org/jira/browse/ZOOKEEPER-137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Reed updated ZOOKEEPER-137: Hadoop Flags: [Reviewed] +1 Looks good > client watcher objects can lose events > -- > > Key: ZOOKEEPER-137 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-137 > Project: Zookeeper > Issue Type: Bug > Components: java client >Affects Versions: 3.0.0 >Reporter: Patrick Hunt >Assignee: Patrick Hunt > Fix For: 3.0.0 > > Attachments: ZOOKEEPER-137.patch > > > if a single watcher (A) is registered on a single node for both a getdata and > exists watch the second watch event may be lost: > 1) getdata("node", A) > 2) setdata("node"...) > 3) exists("node", A) > 4) delete("node"...) > if watch events for 2 is processed on the client (zookeeper.java, zkwatcher) > after 3 completes then the zkwatcher process event method will clear the > watch and the subsequent operation's (4) event will be ignored -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-117) threading issues in Leader election
[ https://issues.apache.org/jira/browse/ZOOKEEPER-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Reed updated ZOOKEEPER-117: Hadoop Flags: [Reviewed] +1 Looks good > threading issues in Leader election > --- > > Key: ZOOKEEPER-117 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-117 > Project: Zookeeper > Issue Type: Bug > Components: server >Affects Versions: 3.0.0 >Reporter: Patrick Hunt >Assignee: Flavio Paiva Junqueira > Fix For: 3.0.0 > > Attachments: ZOOKEEPER-117.patch, ZOOKEEPER-117.patch > > > Leader.lead() creates a new thread that can never terminate (short of > restarting vm) > naked notifyall in lead() method - what is the condition variable? Best if > set inside the sync block -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-38) headers (version+) in log/snap files
[ https://issues.apache.org/jira/browse/ZOOKEEPER-38?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634267#action_12634267 ] Benjamin Reed commented on ZOOKEEPER-38: This looks great Mahadev. Just small comments: - In ZooKeeperServerMain you changed from using the configuration methods to putting everything in the constructor. I think we should stick with the configuration methods. (This same comment applies to Leader and QuorumPeer - In FileSnapLog.deserialize() if the snapshot is bad, you should try an earlier snapshot. (We should add a test case for this) - SnapLog should really be called Snapshot since it does not have a log component - In FileTxnLog.getLogFiles() you should add a comment to the first (fzxid > logZxid) check that you are taking advantage of the fact that the files are sorted, so the last time this condition is true will be for the log file that has snapshotZxid. - In FileTxnLog.getLastLoggedZxid() the comment is a bit unclear. I think this method will also have a problem if the last logfile consists of a single corrupt entry. - In FileTxnLog.truncate() you may need to delete files as well if the zxid you are truncing to is in a log file before the last file - TxnLogCompletion is not used and should be removed - The Util class has some methods that are not used that should be removed. > headers (version+) in log/snap files > > > Key: ZOOKEEPER-38 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-38 > Project: Zookeeper > Issue Type: New Feature > Components: server >Reporter: Patrick Hunt >Assignee: Mahadev konar > Fix For: 3.0.0 > > Attachments: ZOOKEEPER-38.patch, ZOOKEEPER-38.patch, > ZOOKEEPER-38.patch, ZOOKEEPER-38_1.patch, ZOOKEEPER-38_2.patch, > ZOOKEEPER-38_3.patch, ZOOKEEPER-38_5.patch, ZOOKEEPER-38_6.patch, > ZOOKEEPER-38_7.patch > > > Moved from SourceForge to Apache. > http://sourceforge.net/tracker/index.php?func=detail&aid=1961767&group_id=209147&atid=1008547 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-137) client watcher objects can lose events
[ https://issues.apache.org/jira/browse/ZOOKEEPER-137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Reed updated ZOOKEEPER-137: Resolution: Fixed Status: Resolved (was: Patch Available) Committed revision 698734. > client watcher objects can lose events > -- > > Key: ZOOKEEPER-137 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-137 > Project: Zookeeper > Issue Type: Bug > Components: java client >Affects Versions: 3.0.0 >Reporter: Patrick Hunt >Assignee: Patrick Hunt > Fix For: 3.0.0 > > Attachments: ZOOKEEPER-137.patch > > > if a single watcher (A) is registered on a single node for both a getdata and > exists watch the second watch event may be lost: > 1) getdata("node", A) > 2) setdata("node"...) > 3) exists("node", A) > 4) delete("node"...) > if watch events for 2 is processed on the client (zookeeper.java, zkwatcher) > after 3 completes then the zkwatcher process event method will clear the > watch and the subsequent operation's (4) event will be ignored -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-117) threading issues in Leader election
[ https://issues.apache.org/jira/browse/ZOOKEEPER-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Reed updated ZOOKEEPER-117: Resolution: Fixed Status: Resolved (was: Patch Available) Committed revision 698743. > threading issues in Leader election > --- > > Key: ZOOKEEPER-117 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-117 > Project: Zookeeper > Issue Type: Bug > Components: server >Affects Versions: 3.0.0 >Reporter: Patrick Hunt >Assignee: Flavio Paiva Junqueira > Fix For: 3.0.0 > > Attachments: ZOOKEEPER-117.patch, ZOOKEEPER-117.patch > > > Leader.lead() creates a new thread that can never terminate (short of > restarting vm) > naked notifyall in lead() method - what is the condition variable? Best if > set inside the sync block -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-139) Create Enums for WatcherEvent's KeeperState and EventType
[ https://issues.apache.org/jira/browse/ZOOKEEPER-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jakob Homan updated ZOOKEEPER-139: -- Attachment: ZOOKEEPER-139.patch Updated patch to not change the jute code. The Jute type is still WatcherEvent. The type used by users is called WatchedEvent (for lack of any better term). Otherwise the same. Updated to work with changes from ZOOKEEPER-137. > Create Enums for WatcherEvent's KeeperState and EventType > - > > Key: ZOOKEEPER-139 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-139 > Project: Zookeeper > Issue Type: Sub-task >Affects Versions: 3.0.0 >Reporter: Jakob Homan >Assignee: Jakob Homan > Fix For: 3.0.0 > > Attachments: ZOOKEEPER-139.patch, ZOOKEEPER-139.patch, > ZOOKEEPER-139.patch > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-139) Create Enums for WatcherEvent's KeeperState and EventType
[ https://issues.apache.org/jira/browse/ZOOKEEPER-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jakob Homan updated ZOOKEEPER-139: -- Status: Patch Available (was: Open) > Create Enums for WatcherEvent's KeeperState and EventType > - > > Key: ZOOKEEPER-139 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-139 > Project: Zookeeper > Issue Type: Sub-task >Affects Versions: 3.0.0 >Reporter: Jakob Homan >Assignee: Jakob Homan > Fix For: 3.0.0 > > Attachments: ZOOKEEPER-139.patch, ZOOKEEPER-139.patch, > ZOOKEEPER-139.patch > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-93) Create Documentation for Zookeeper
[ https://issues.apache.org/jira/browse/ZOOKEEPER-93?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-93: -- Attachment: (was: ZOOKEEPER-93.patch) > Create Documentation for Zookeeper > -- > > Key: ZOOKEEPER-93 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-93 > Project: Zookeeper > Issue Type: Task > Components: documentation >Affects Versions: 3.0.0 > Environment: N/A >Reporter: Robbie Scott > Fix For: 3.0.0 > > Attachments: ZOOKEEPER-93.tar.gz > > Original Estimate: 0.02h > Remaining Estimate: 0.02h > > Initial version of the documentation, migrated from source forge. > Reorganizing, expanding. Initial goal is to port Source Forge documentation > into Forrest. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (ZOOKEEPER-93) Create Documentation for Zookeeper
[ https://issues.apache.org/jira/browse/ZOOKEEPER-93?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt reassigned ZOOKEEPER-93: - Assignee: Patrick Hunt > Create Documentation for Zookeeper > -- > > Key: ZOOKEEPER-93 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-93 > Project: Zookeeper > Issue Type: Task > Components: documentation >Affects Versions: 3.0.0 > Environment: N/A >Reporter: Robbie Scott >Assignee: Patrick Hunt > Fix For: 3.0.0 > > Attachments: ZOOKEEPER-93.tar.gz > > Original Estimate: 0.02h > Remaining Estimate: 0.02h > > Initial version of the documentation, migrated from source forge. > Reorganizing, expanding. Initial goal is to port Source Forge documentation > into Forrest. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-93) Create Documentation for Zookeeper
[ https://issues.apache.org/jira/browse/ZOOKEEPER-93?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-93: -- Attachment: ZOOKEEPER-93.tar.gz This tar file attachment is the latest update from Robbie (tech writer). untar in your trunk, open browser on docs/index.html to view. Please review ASAP and I will commit and work through the publishing process to get up on the site. > Create Documentation for Zookeeper > -- > > Key: ZOOKEEPER-93 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-93 > Project: Zookeeper > Issue Type: Task > Components: documentation >Affects Versions: 3.0.0 > Environment: N/A >Reporter: Robbie Scott > Fix For: 3.0.0 > > Attachments: ZOOKEEPER-93.tar.gz > > Original Estimate: 0.02h > Remaining Estimate: 0.02h > > Initial version of the documentation, migrated from source forge. > Reorganizing, expanding. Initial goal is to port Source Forge documentation > into Forrest. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-93) Create Documentation for Zookeeper
[ https://issues.apache.org/jira/browse/ZOOKEEPER-93?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-93: -- Status: Patch Available (was: Open) > Create Documentation for Zookeeper > -- > > Key: ZOOKEEPER-93 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-93 > Project: Zookeeper > Issue Type: Task > Components: documentation >Affects Versions: 3.0.0 > Environment: N/A >Reporter: Robbie Scott >Assignee: Patrick Hunt > Fix For: 3.0.0 > > Attachments: ZOOKEEPER-93.tar.gz > > Original Estimate: 0.02h > Remaining Estimate: 0.02h > > Initial version of the documentation, migrated from source forge. > Reorganizing, expanding. Initial goal is to port Source Forge documentation > into Forrest. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-93) Create Documentation for Zookeeper
[ https://issues.apache.org/jira/browse/ZOOKEEPER-93?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Reed updated ZOOKEEPER-93: --- Hadoop Flags: [Reviewed] +1 commit. When you commit, you should probably remove docs/src/documentation/resources/images/architecture.gif since we don't use it. > Create Documentation for Zookeeper > -- > > Key: ZOOKEEPER-93 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-93 > Project: Zookeeper > Issue Type: Task > Components: documentation >Affects Versions: 3.0.0 > Environment: N/A >Reporter: Robbie Scott >Assignee: Patrick Hunt > Fix For: 3.0.0 > > Attachments: ZOOKEEPER-93.tar.gz > > Original Estimate: 0.02h > Remaining Estimate: 0.02h > > Initial version of the documentation, migrated from source forge. > Reorganizing, expanding. Initial goal is to port Source Forge documentation > into Forrest. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-93) Create Documentation for Zookeeper
[ https://issues.apache.org/jira/browse/ZOOKEEPER-93?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-93: -- Resolution: Fixed Status: Resolved (was: Patch Available) Committed revision 698787. > Create Documentation for Zookeeper > -- > > Key: ZOOKEEPER-93 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-93 > Project: Zookeeper > Issue Type: Task > Components: documentation >Affects Versions: 3.0.0 > Environment: N/A >Reporter: Robbie Scott >Assignee: Patrick Hunt > Fix For: 3.0.0 > > Attachments: ZOOKEEPER-93.tar.gz > > Original Estimate: 0.02h > Remaining Estimate: 0.02h > > Initial version of the documentation, migrated from source forge. > Reorganizing, expanding. Initial goal is to port Source Forge documentation > into Forrest. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (ZOOKEEPER-142) Provide Javadoc as to the maximum size of the data byte array that may be stored within a znode
Provide Javadoc as to the maximum size of the data byte array that may be stored within a znode --- Key: ZOOKEEPER-142 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-142 Project: Zookeeper Issue Type: Improvement Components: java client Affects Versions: 3.0.0 Reporter: Jakob Homan Assignee: Jakob Homan Fix For: 3.0.0 Currently there is nothing in the API documentation as to the maximum size of the data in a znode. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-142) Provide Javadoc as to the maximum size of the data byte array that may be stored within a znode
[ https://issues.apache.org/jira/browse/ZOOKEEPER-142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jakob Homan updated ZOOKEEPER-142: -- Attachment: ZOOKEEPER-142.patch This patch: * Adds verbage to the Javadoc for ZooKeeper.create and ZooKeeper.setData about the 1 mb limit of data in a znode. Also, when I was testing this, I found that passing a large-than-1-mb byte array caused the client to be disconnected, along with the KeeperException being thrown. Is disconnection correct in this case? I'm not sure, just asking. Seems a bit harsh. > Provide Javadoc as to the maximum size of the data byte array that may be > stored within a znode > --- > > Key: ZOOKEEPER-142 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-142 > Project: Zookeeper > Issue Type: Improvement > Components: java client >Affects Versions: 3.0.0 >Reporter: Jakob Homan >Assignee: Jakob Homan > Fix For: 3.0.0 > > Attachments: ZOOKEEPER-142.patch > > > Currently there is nothing in the API documentation as to the maximum size of > the data in a znode. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-142) Provide Javadoc as to the maximum size of the data byte array that may be stored within a znode
[ https://issues.apache.org/jira/browse/ZOOKEEPER-142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jakob Homan updated ZOOKEEPER-142: -- Status: Patch Available (was: Open) > Provide Javadoc as to the maximum size of the data byte array that may be > stored within a znode > --- > > Key: ZOOKEEPER-142 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-142 > Project: Zookeeper > Issue Type: Improvement > Components: java client >Affects Versions: 3.0.0 >Reporter: Jakob Homan >Assignee: Jakob Homan > Fix For: 3.0.0 > > Attachments: ZOOKEEPER-142.patch > > > Currently there is nothing in the API documentation as to the maximum size of > the data in a znode. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-142) Provide Javadoc as to the maximum size of the data byte array that may be stored within a znode
[ https://issues.apache.org/jira/browse/ZOOKEEPER-142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jakob Homan updated ZOOKEEPER-142: -- Priority: Trivial (was: Major) > Provide Javadoc as to the maximum size of the data byte array that may be > stored within a znode > --- > > Key: ZOOKEEPER-142 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-142 > Project: Zookeeper > Issue Type: Improvement > Components: java client >Affects Versions: 3.0.0 >Reporter: Jakob Homan >Assignee: Jakob Homan >Priority: Trivial > Fix For: 3.0.0 > > Attachments: ZOOKEEPER-142.patch > > > Currently there is nothing in the API documentation as to the maximum size of > the data in a znode. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.