[jira] Commented: (ZOOKEEPER-446) some traces of the host auth scheme left
[ https://issues.apache.org/jira/browse/ZOOKEEPER-446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12723039#action_12723039 ] Hudson commented on ZOOKEEPER-446: -- Integrated in ZooKeeper-trunk #355 (See [http://hudson.zones.apache.org/hudson/job/ZooKeeper-trunk/355/]) . some traces of the host auth scheme left (breed via mahadev) some traces of the host auth scheme left Key: ZOOKEEPER-446 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-446 Project: Zookeeper Issue Type: Bug Reporter: Benjamin Reed Assignee: Benjamin Reed Fix For: 3.2.0 Attachments: ZOOKEEPER-446.patch the host auth scheme was removed because it used a blocking call in an async pipeline. however, tragically, the blocking call was not removed including a couple of other stray classes. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-356) Masking bookie failure during writes to a ledger
[ https://issues.apache.org/jira/browse/ZOOKEEPER-356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12723150#action_12723150 ] Benjamin Reed commented on ZOOKEEPER-356: - just a couple of things: * in BookieHandle, why doesn't stop get set to true on shutdown? * you need to check all your uses of LOG.info most of them seem to really be LOG.debug * in ClientCBWorker stop should be volatile * in LedgerHandle shouldn't add/removeBookie be synchronized? * in QuorumEngine should idCounter be synchronized? * In BookieClient you do a new IOException(), you should provide some hint of the problem in the constructor Masking bookie failure during writes to a ledger Key: ZOOKEEPER-356 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-356 Project: Zookeeper Issue Type: New Feature Components: contrib-bookkeeper Reporter: Flavio Paiva Junqueira Assignee: Flavio Paiva Junqueira Fix For: 3.2.0 Attachments: ZOOKEEPER-356.patch, ZOOKEEPER-356.patch, ZOOKEEPER-356.patch, ZOOKEEPER-356.patch, ZOOKEEPER-356.patch, ZOOKEEPER-356.patch, ZOOKEEPER-BOOKKEEPER-356.patch The idea of this jira is to work out the changes necessary to make a client mask the failure of a bookie while writing to a ledger. I'm submitting a preliminary patch, but before I submit a final one, I need to have 288 committed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-224) Deploy ZooKeeper 3.2.0 to a Maven Repository
[ https://issues.apache.org/jira/browse/ZOOKEEPER-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12723182#action_12723182 ] Benjamin Reed commented on ZOOKEEPER-224: - why do we need ivy? can't we just run the command outside the build process after we do the release? Deploy ZooKeeper 3.2.0 to a Maven Repository Key: ZOOKEEPER-224 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-224 Project: Zookeeper Issue Type: Task Components: build Affects Versions: 3.0.0 Reporter: Hiram Chirino Assignee: Patrick Hunt Priority: Critical Fix For: 3.2.0 I've created the maven poms needed for the 3.0.0 release. The directory structure and artifacts located at: http://people.apache.org/~chirino/zk-repo/ aka people.apache.org:/x1/users/chirino/public_html/zk-repo Just need sto get GPG signed by the project KEY and deployed to: people.apache.org:/www/people.apache.org/repo/m2-ibiblio-rsync-repository Who's the current ZooKeeper release manager? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-356) Masking bookie failure during writes to a ledger
[ https://issues.apache.org/jira/browse/ZOOKEEPER-356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flavio Paiva Junqueira updated ZOOKEEPER-356: - Attachment: ZOOKEEPER-356.patch Masking bookie failure during writes to a ledger Key: ZOOKEEPER-356 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-356 Project: Zookeeper Issue Type: New Feature Components: contrib-bookkeeper Reporter: Flavio Paiva Junqueira Assignee: Flavio Paiva Junqueira Fix For: 3.2.0 Attachments: ZOOKEEPER-356.patch, ZOOKEEPER-356.patch, ZOOKEEPER-356.patch, ZOOKEEPER-356.patch, ZOOKEEPER-356.patch, ZOOKEEPER-356.patch, ZOOKEEPER-356.patch, ZOOKEEPER-BOOKKEEPER-356.patch The idea of this jira is to work out the changes necessary to make a client mask the failure of a bookie while writing to a ledger. I'm submitting a preliminary patch, but before I submit a final one, I need to have 288 committed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-224) Deploy ZooKeeper 3.2.0 to a Maven Repository
[ https://issues.apache.org/jira/browse/ZOOKEEPER-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12723211#action_12723211 ] Doug Cutting commented on ZOOKEEPER-224: why do we need ivy? Ivy seems to be the best way to integrate Ant-based projects into the Maven world. You write an Ivy config that lists the jars you depend on, and Ivy fetches them, so that you no longer need to include them in svn. It can generate a POM file from its configuration, so that applications that depend on Zookeeper can easily get it and its dependencies. If you maintain your POM file manually, then each time you add or upgrade a lib you have to update multiple places, while with Ivy you only list your dependencies in one place. I think Ivy can also push releases into Maven repos, but I haven't tried that yet. I think this can also be done manually just by copying the .jar, .md5, .sha1, .pom, and .asc files to the right directory on people.apache.org. I did a simplisitic conversion of Avro to Ivy (AVRO-53, http://svn.apache.org/viewvc?view=revrevision=785776). The build.xml now generates all of the files but the .asc. When I first try to do a release I'll learn whether this works! Deploy ZooKeeper 3.2.0 to a Maven Repository Key: ZOOKEEPER-224 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-224 Project: Zookeeper Issue Type: Task Components: build Affects Versions: 3.0.0 Reporter: Hiram Chirino Assignee: Patrick Hunt Priority: Critical Fix For: 3.2.0 I've created the maven poms needed for the 3.0.0 release. The directory structure and artifacts located at: http://people.apache.org/~chirino/zk-repo/ aka people.apache.org:/x1/users/chirino/public_html/zk-repo Just need sto get GPG signed by the project KEY and deployed to: people.apache.org:/www/people.apache.org/repo/m2-ibiblio-rsync-repository Who's the current ZooKeeper release manager? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-356) Masking bookie failure during writes to a ledger
[ https://issues.apache.org/jira/browse/ZOOKEEPER-356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flavio Paiva Junqueira updated ZOOKEEPER-356: - Attachment: ZOOKEEPER-356.patch Synchronizing LedgerHandle::removeBookie(). Masking bookie failure during writes to a ledger Key: ZOOKEEPER-356 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-356 Project: Zookeeper Issue Type: New Feature Components: contrib-bookkeeper Reporter: Flavio Paiva Junqueira Assignee: Flavio Paiva Junqueira Fix For: 3.2.0 Attachments: ZOOKEEPER-356.patch, ZOOKEEPER-356.patch, ZOOKEEPER-356.patch, ZOOKEEPER-356.patch, ZOOKEEPER-356.patch, ZOOKEEPER-356.patch, ZOOKEEPER-356.patch, ZOOKEEPER-356.patch, ZOOKEEPER-BOOKKEEPER-356.patch The idea of this jira is to work out the changes necessary to make a client mask the failure of a bookie while writing to a ledger. I'm submitting a preliminary patch, but before I submit a final one, I need to have 288 committed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-315) add forrest docs for bookkeeper.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahadev konar updated ZOOKEEPER-315: Resolution: Fixed Status: Resolved (was: Patch Available) I just committed this. good work on the forrest docs flavio... thanks... add forrest docs for bookkeeper. Key: ZOOKEEPER-315 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-315 Project: Zookeeper Issue Type: Improvement Components: contrib-bookkeeper Affects Versions: 3.1.0 Reporter: Mahadev konar Assignee: Flavio Paiva Junqueira Priority: Blocker Fix For: 3.2.0 Attachments: ZOOKEEPER-315.patch, ZOOKEEPER-315.patch, ZOOKEEPER-315.patch we should have forrest docs for bookkeeper for - how to install bookkeeper - usage model - programming examples for users - FAQ -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-224) Deploy ZooKeeper 3.2.0 to a Maven Repository
[ https://issues.apache.org/jira/browse/ZOOKEEPER-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12723247#action_12723247 ] Benjamin Reed commented on ZOOKEEPER-224: - sorry, i should have scoped my question better. i mean why do we need ivy to push our release jars into the repository?. i can see how we can use ivy for other needs, but for the specific issue of getting our jars into the maven repository, we can just run a command after we do the release. right? Deploy ZooKeeper 3.2.0 to a Maven Repository Key: ZOOKEEPER-224 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-224 Project: Zookeeper Issue Type: Task Components: build Affects Versions: 3.0.0 Reporter: Hiram Chirino Assignee: Patrick Hunt Priority: Critical Fix For: 3.2.0 I've created the maven poms needed for the 3.0.0 release. The directory structure and artifacts located at: http://people.apache.org/~chirino/zk-repo/ aka people.apache.org:/x1/users/chirino/public_html/zk-repo Just need sto get GPG signed by the project KEY and deployed to: people.apache.org:/www/people.apache.org/repo/m2-ibiblio-rsync-repository Who's the current ZooKeeper release manager? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-329) document how to integrate 3rd party authentication into ZK server ACLs
[ https://issues.apache.org/jira/browse/ZOOKEEPER-329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahadev konar updated ZOOKEEPER-329: Resolution: Fixed Status: Resolved (was: Patch Available) I just committed this. thanks ben! document how to integrate 3rd party authentication into ZK server ACLs -- Key: ZOOKEEPER-329 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-329 Project: Zookeeper Issue Type: Improvement Components: documentation Reporter: Patrick Hunt Assignee: Benjamin Reed Priority: Minor Fix For: 3.2.0 Attachments: plugauth.pdf, ZOOKEEPER-329.patch the docs mention that zk supports pluggable auth schemes but doesn't detail the API/examples. We should add this to the docs. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-224) Deploy ZooKeeper 3.2.0 to a Maven Repository
[ https://issues.apache.org/jira/browse/ZOOKEEPER-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12723257#action_12723257 ] Doug Cutting commented on ZOOKEEPER-224: but for the specific issue of getting our jars into the maven repository, we can just run a command after we do the release. right? Moreover, I think you have to. I don't think either Maven or Ivy can sign things correctly. Deploy ZooKeeper 3.2.0 to a Maven Repository Key: ZOOKEEPER-224 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-224 Project: Zookeeper Issue Type: Task Components: build Affects Versions: 3.0.0 Reporter: Hiram Chirino Assignee: Patrick Hunt Priority: Critical Fix For: 3.2.0 I've created the maven poms needed for the 3.0.0 release. The directory structure and artifacts located at: http://people.apache.org/~chirino/zk-repo/ aka people.apache.org:/x1/users/chirino/public_html/zk-repo Just need sto get GPG signed by the project KEY and deployed to: people.apache.org:/www/people.apache.org/repo/m2-ibiblio-rsync-repository Who's the current ZooKeeper release manager? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-417) stray message problem when changing servers
[ https://issues.apache.org/jira/browse/ZOOKEEPER-417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Reed updated ZOOKEEPER-417: Attachment: ZOOKEEPER-417.patch stray message problem when changing servers --- Key: ZOOKEEPER-417 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-417 Project: Zookeeper Issue Type: Bug Reporter: Benjamin Reed Assignee: Benjamin Reed Priority: Blocker Fix For: 3.2.0 Attachments: ZOOKEEPER-417.patch There is a possibility for stray messages from a previous connection to violate ordering and generally cause problems. Here is a scenario: we have a client, C, two followers, F1 and F2, and a leader, L. The client is connected to F1, which is a slow follower. C sends setData(/a, 1) to F1 and then loses the connection, so C reconnects to F2 and sends setData(/a, 2). it is possible, if F1 is slow enough and the setData(/a, 1) got onto the network before the connection break, for F1 to forward the setData(/a, 1) to L after F2 forwards setData(/a, 2). to fix this, the leader should keep track of which follower last registered a session for a client and drop any requests from followers for clients for whom they do not have a registration. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-417) stray message problem when changing servers
[ https://issues.apache.org/jira/browse/ZOOKEEPER-417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Reed updated ZOOKEEPER-417: Status: Patch Available (was: Open) stray message problem when changing servers --- Key: ZOOKEEPER-417 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-417 Project: Zookeeper Issue Type: Bug Reporter: Benjamin Reed Assignee: Benjamin Reed Priority: Blocker Fix For: 3.2.0 Attachments: ZOOKEEPER-417.patch There is a possibility for stray messages from a previous connection to violate ordering and generally cause problems. Here is a scenario: we have a client, C, two followers, F1 and F2, and a leader, L. The client is connected to F1, which is a slow follower. C sends setData(/a, 1) to F1 and then loses the connection, so C reconnects to F2 and sends setData(/a, 2). it is possible, if F1 is slow enough and the setData(/a, 1) got onto the network before the connection break, for F1 to forward the setData(/a, 1) to L after F2 forwards setData(/a, 2). to fix this, the leader should keep track of which follower last registered a session for a client and drop any requests from followers for clients for whom they do not have a registration. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Build failed in Hudson: Zookeeper-Patch-vesta.apache.org #128
See http://hudson.zones.apache.org/hudson/job/Zookeeper-Patch-vesta.apache.org/128/changes Changes: [mahadev] ZOOKEEPER-329. document how to integrate 3rd party authentication into ZK server ACLs. (breed via mahadev) [mahadev] ZOOKEEPER-315. add forrest docs for bookkeeper. (flavio via mahadev) [mahadev] ZOOKEEPER-446. some traces of the host auth scheme left (breed via mahadev) [mahadev] fixing externals property for test patch. -- started Building remotely on vesta.apache.org (Ubuntu) Updating http://svn.apache.org/repos/asf/hadoop/zookeeper/trunk U CHANGES.txt G src/java/test/org/apache/zookeeper/test/ACLTest.java Usrc/java/test G src/java/main/org/apache/zookeeper/server/NIOServerCnxn.java D src/java/main/org/apache/zookeeper/server/auth/HostAuthenticationProvider.java G src/java/main/org/apache/zookeeper/server/auth/ProviderRegistry.java A src/docs/src/documentation/content/xdocs/bookkeeperProgrammer.xml U src/docs/src/documentation/content/xdocs/zookeeperProgrammers.xml U src/docs/src/documentation/content/xdocs/zookeeperTutorial.xml U src/docs/src/documentation/content/xdocs/site.xml U src/docs/src/documentation/content/xdocs/index.xml A src/docs/src/documentation/content/xdocs/bookkeeperConfig.xml A src/docs/src/documentation/content/xdocs/bookkeeperStarted.xml A src/docs/src/documentation/content/xdocs/bookkeeperOverview.xml U docs/zookeeperAdmin.html A docs/bookkeeperStarted.html U docs/zookeeperJMX.html A docs/bookkeeperOverview.pdf A docs/bookkeeperProgrammer.html A docs/bookkeeperProgrammer.pdf U docs/zookeeperTutorial.html U docs/releasenotes.html U docs/linkmap.html U docs/javaExample.html U docs/zookeeperQuotas.html U docs/index.pdf A docs/bookkeeperConfig.html A docs/bookkeeperOverview.html A docs/bookkeeperConfig.pdf A docs/bookkeeperStarted.pdf U docs/zookeeperProgrammers.html U docs/zookeeperInternals.html U docs/zookeeperProgrammers.pdf U docs/zookeeperStarted.html U docs/recipes.html U docs/zookeeperTutorial.pdf U docs/zookeeperOver.html U docs/linkmap.pdf U docs/index.html Fetching 'http://svn.apache.org/repos/asf/hadoop/common/nightly/test-patch' at -1 into 'http://hudson.zones.apache.org/hudson/job/Zookeeper-Patch-vesta.apache.org/ws/trunk/src/java/test/bin' At revision 787892 At revision 787892 no revision recorded for http://svn.apache.org/repos/asf/hadoop/common/nightly/test-patch in the previous build [Zookeeper-Patch-vesta.apache.org] $ /bin/bash /tmp/hudson213266760860977689.sh /home/hudson/tools/java/latest1.6/bin/java Buildfile: build.xml check-for-findbugs: findbugs.check: java5.check: forrest.check: hudson-test-patch: [exec] [exec] [exec] == [exec] == [exec] Testing patch for ZOOKEEPER-315. [exec] == [exec] == [exec] [exec] [exec] [exec] Fetching external item into 'src/java/test/bin' [exec] Asrc/java/test/bin/test-patch.sh [exec] Updated external to revision 787892. [exec] [exec] Updated to revision 787892. [exec] ZOOKEEPER-315 is not Patch Available. Exiting. [exec] % Total% Received % Xferd Average Speed TimeTime Time Current [exec] Dload Upload Total Spent Left Speed [exec] [exec] [exec] [exec] == [exec] == [exec] Finished build. [exec] == [exec] == [exec] [exec] [exec] 0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0 0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0 BUILD SUCCESSFUL Total time: 3 seconds ERROR: No artifacts found that match the file pattern trunk/build/test/findbugs/newPatchFindbugsWarnings.html,trunk/patchprocess/*Warnings.txt. Configuration error? ERROR: 'trunk/build/test/findbugs/newPatchFindbugsWarnings.html' doesn't match anything: 'trunk' exists but not 'trunk/build/test/findbugs/newPatchFindbugsWarnings.html' Recording test results Description found: ZOOKEEPER-315
[jira] Commented: (ZOOKEEPER-237) Add a Chroot request
[ https://issues.apache.org/jira/browse/ZOOKEEPER-237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12723430#action_12723430 ] Hadoop QA commented on ZOOKEEPER-237: - +1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12411450/ZOOKEEPER-237.patch against trunk revision 787789. +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 23 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 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: http://hudson.zones.apache.org/hudson/job/Zookeeper-Patch-vesta.apache.org/129/testReport/ Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Zookeeper-Patch-vesta.apache.org/129/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Console output: http://hudson.zones.apache.org/hudson/job/Zookeeper-Patch-vesta.apache.org/129/console This message is automatically generated. Add a Chroot request Key: ZOOKEEPER-237 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-237 Project: Zookeeper Issue Type: New Feature Components: c client, java client Reporter: Benjamin Reed Assignee: Mahadev konar Priority: Minor Fix For: 3.2.0 Attachments: ZOOKEEPER-237.patch, ZOOKEEPER-237.patch, ZOOKEEPER-237.patch It would be nice to be able to root ZooKeeper handles at specific points in the namespace, so that applications that use ZooKeeper can work in their own rooted subtree. For example, if ops decides that application X can use the subtree /apps/X and application Y can use the subtree /apps/Y, X can to a chroot to /apps/X and then all its path references can be rooted at /apps/X. Thus when X creates the path /myid, it will actually be creating the path /apps/X/myid. There are two ways we can expose this mechanism: 1) We can simply add a chroot(String path) API, or 2) we can integrate into a service identifier scheme for example zk://server1:2181,server2:2181/my/root. I like the second form personally. -- 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-Patch-vesta.apache.org #129
See http://hudson.zones.apache.org/hudson/job/Zookeeper-Patch-vesta.apache.org/129/
[jira] Updated: (ZOOKEEPER-356) Masking bookie failure during writes to a ledger
[ https://issues.apache.org/jira/browse/ZOOKEEPER-356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Reed updated ZOOKEEPER-356: Issue Type: Improvement (was: New Feature) Masking bookie failure during writes to a ledger Key: ZOOKEEPER-356 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-356 Project: Zookeeper Issue Type: Improvement Components: contrib-bookkeeper Reporter: Flavio Paiva Junqueira Assignee: Flavio Paiva Junqueira Fix For: 3.2.0 Attachments: ZOOKEEPER-356.patch, ZOOKEEPER-356.patch, ZOOKEEPER-356.patch, ZOOKEEPER-356.patch, ZOOKEEPER-356.patch, ZOOKEEPER-356.patch, ZOOKEEPER-356.patch, ZOOKEEPER-356.patch, ZOOKEEPER-BOOKKEEPER-356.patch The idea of this jira is to work out the changes necessary to make a client mask the failure of a bookie while writing to a ledger. I'm submitting a preliminary patch, but before I submit a final one, I need to have 288 committed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-356) Masking bookie failure during writes to a ledger
[ https://issues.apache.org/jira/browse/ZOOKEEPER-356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Reed updated ZOOKEEPER-356: Resolution: Fixed Status: Resolved (was: Patch Available) Committed revision 787907. Masking bookie failure during writes to a ledger Key: ZOOKEEPER-356 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-356 Project: Zookeeper Issue Type: Improvement Components: contrib-bookkeeper Reporter: Flavio Paiva Junqueira Assignee: Flavio Paiva Junqueira Fix For: 3.2.0 Attachments: ZOOKEEPER-356.patch, ZOOKEEPER-356.patch, ZOOKEEPER-356.patch, ZOOKEEPER-356.patch, ZOOKEEPER-356.patch, ZOOKEEPER-356.patch, ZOOKEEPER-356.patch, ZOOKEEPER-356.patch, ZOOKEEPER-BOOKKEEPER-356.patch The idea of this jira is to work out the changes necessary to make a client mask the failure of a bookie while writing to a ledger. I'm submitting a preliminary patch, but before I submit a final one, I need to have 288 committed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
