[jira] Commented: (ZOOKEEPER-464) Need procedure to garbage collect ledgers
[ https://issues.apache.org/jira/browse/ZOOKEEPER-464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12867431#action_12867431 ] Flavio Paiva Junqueira commented on ZOOKEEPER-464: -- Erwin pointed out that I forgot to add two new files, so here they are: Committed revision 944140. Need procedure to garbage collect ledgers - Key: ZOOKEEPER-464 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-464 Project: Zookeeper Issue Type: New Feature Components: contrib-bookkeeper Reporter: Flavio Paiva Junqueira Assignee: Erwin Tam Fix For: 3.4.0 Attachments: zookeeper-464-log.txt, ZOOKEEPER-464.patch, ZOOKEEPER-464.patch, ZOOKEEPER-464.patch, ZOOKEEPER-464.patch An application using BookKeeper is likely to use a large number of ledgers over time. Such an application might not need all ledgers created over time and might want to delete some of these ledgers to free up some space on bookies. The idea of this jira is to implement a procedure that enables an application to garbage-collect unwanted ledgers. To garbage-collect a ledger, we need to delete the ledger metadata on ZooKeeper, and delete the ledger data on corresponding bookies. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-774) Recipes tests are slightly outdated: they do not compile against JUnit 4.8
[ https://issues.apache.org/jira/browse/ZOOKEEPER-774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12867450#action_12867450 ] Hadoop QA commented on ZOOKEEPER-774: - +1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12444341/ZOOKEEPER-774.patch against trunk revision 944140. +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 21 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-h1.grid.sp2.yahoo.net/91/testReport/ Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Zookeeper-Patch-h1.grid.sp2.yahoo.net/91/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Console output: http://hudson.zones.apache.org/hudson/job/Zookeeper-Patch-h1.grid.sp2.yahoo.net/91/console This message is automatically generated. Recipes tests are slightly outdated: they do not compile against JUnit 4.8 -- Key: ZOOKEEPER-774 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-774 Project: Zookeeper Issue Type: Bug Components: recipes Affects Versions: 3.3.0 Reporter: Sergey Doroshenko Assignee: Sergey Doroshenko Priority: Minor Fix For: 3.4.0 Attachments: ZOOKEEPER-774.patch As title -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [VOTE] Release ZooKeeper 3.3.1 (candidate 0)
With 6 +1's (3 PMC) and no -1's the vote passes. I'm working to publish the release and will send announcements as soon as that's done. Patrick On 05/13/2010 10:51 PM, Stack wrote: +1 I installed it under hbase cluster as a 5-node ensemble. Looks like it works like 3.3.0. Did some messing sending nc commands. No prob. St.Ack On Thu, May 13, 2010 at 4:52 PM, Mahadev Konarmaha...@yahoo-inc.com wrote: +1. Ran ant tests and some manual testing to bring up a cluster and run manual commands on the zookeeper cluster of 1,3, 5 nodes. Thanks Mahadev On 5/11/10 10:32 PM, Patrick Huntph...@apache.org wrote: +1, tests pass for me, also verified that nc/zktop worked properly on a real cluster (4letter word fix). Patrick On 05/07/2010 11:25 AM, Patrick Hunt wrote: I've created a candidate build for ZooKeeper 3.3.1. This is a bug fix release addressing seventeen issues (one critical) -- see the release notes for details. *** Please download, test and VOTE before the *** vote closes 11am pacific time, Wednesday, May 12.*** http://people.apache.org/~phunt/zookeeper-3.3.1-candidate-0/ Should we release this? Patrick
[jira] Updated: (ZOOKEEPER-774) Recipes tests are slightly outdated: they do not compile against JUnit 4.8
[ https://issues.apache.org/jira/browse/ZOOKEEPER-774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-774: --- Status: Resolved (was: Patch Available) Hadoop Flags: [Reviewed] Resolution: Fixed +1 thanks Sergey! Recipes tests are slightly outdated: they do not compile against JUnit 4.8 -- Key: ZOOKEEPER-774 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-774 Project: Zookeeper Issue Type: Bug Components: recipes Affects Versions: 3.3.0 Reporter: Sergey Doroshenko Assignee: Sergey Doroshenko Priority: Minor Fix For: 3.4.0 Attachments: ZOOKEEPER-774.patch As title -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-767) Submitting Demo/Recipe Shared / Exclusive Lock Code
[ https://issues.apache.org/jira/browse/ZOOKEEPER-767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-767: --- Status: Open (was: Patch Available) Hi Sam, putting one's own copyright notice as done in this latest patch is against Apache policy (sort of like how we don't allow @author tags in the javadoc). One problem is that then everyone who patches the file is tempted to add a copyright for their contributions, this gets ugly fast. We don't try to fully document the reality of the copyright ownership in the source however the commit log / scm will document it, though. Also what you've added for the license is not the normal Apache boilerplate. It does not include the reference to NOTICE for copyright info like it should, it should also be at the very top of the file. Please update your patch with the following file header. (should be at the top of each source file, see the other files in this directory for examples). Thanks! /** * Licensed to the Apache Software Foundation (ASF) under one * or more contributor license agreements. See the NOTICE file * distributed with this work for additional information * regarding copyright ownership. The ASF licenses this file * to you under the Apache License, Version 2.0 (the * License); you may not use this file except in compliance * with the License. You may obtain a copy of the License at * * http://www.apache.org/licenses/LICENSE-2.0 * * Unless required by applicable law or agreed to in writing, software * distributed under the License is distributed on an AS IS BASIS, * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. * See the License for the specific language governing permissions and * limitations under the License. */ Submitting Demo/Recipe Shared / Exclusive Lock Code --- Key: ZOOKEEPER-767 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-767 Project: Zookeeper Issue Type: Improvement Components: recipes Affects Versions: 3.3.0 Reporter: Sam Baskinger Assignee: Sam Baskinger Priority: Minor Fix For: 3.4.0 Attachments: ZOOKEEPER-767.patch Networked Insights would like to share-back some code for shared/exclusive locking that we are using in our labs. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
