[jira] Commented: (ZOOKEEPER-69) ZooKeeper logo
[ https://issues.apache.org/jira/browse/ZOOKEEPER-69?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12650449#action_12650449 ] Jeff Hammerbacher commented on ZOOKEEPER-69: http://www.99designs.com or http://logoworks.com will get you a well-designed logo for a good price (under $1K), if it's in the YHOO budget... > ZooKeeper logo > -- > > Key: ZOOKEEPER-69 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-69 > Project: Zookeeper > Issue Type: Wish > Components: documentation >Reporter: Flavio Paiva Junqueira >Assignee: Benjamin Reed >Priority: Minor > Fix For: 3.1.0 > > Attachments: pbzk.gif, zk_logo_use.png, zk_logo_use2.png, > zookeeper-sketch.jpg > > > I think we need a cool logo for the project. The ones I've seen so far are a > little lame, and that includes the one I've created for SourceForge. If > anyone on this list has an idea or knows of anyone with some art skills, > plese add a commento to this Jira. -- 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.0.1 (candidate 1)
+1 .. I ran ant test and some command line testing on a quorum of 3 on a single node. mahadev On 11/24/08 5:50 PM, "Patrick Hunt" <[EMAIL PROTECTED]> wrote: > I've created a second candidate build for ZooKeeper 3.0.1. > > *** Please download, test and VOTE before the > *** vote closes EOD on Friday, November 28.*** > > http://people.apache.org/~phunt/zookeeper-3.0.1-candidate-1/ > > The only change to rc1 from rc0 is adding a missing apache license > header to a source file: > https://issues.apache.org/jira/browse/ZOOKEEPER-232 > > Should we release this? > > Patrick >
RE: [VOTE] Release ZooKeeper 3.0.1 (candidate 1)
+1 This candidate passes our tests. Thanks again Patrick! Stu -Original Message- From: "Patrick Hunt" <[EMAIL PROTECTED]> Sent: Monday, November 24, 2008 8:50pm To: zookeeper-dev@hadoop.apache.org Subject: [VOTE] Release ZooKeeper 3.0.1 (candidate 1) I've created a second candidate build for ZooKeeper 3.0.1. *** Please download, test and VOTE before the *** vote closes EOD on Friday, November 28.*** http://people.apache.org/~phunt/zookeeper-3.0.1-candidate-1/ The only change to rc1 from rc0 is adding a missing apache license header to a source file: https://issues.apache.org/jira/browse/ZOOKEEPER-232 Should we release this? Patrick
[VOTE] Release ZooKeeper 3.0.1 (candidate 1)
I've created a second candidate build for ZooKeeper 3.0.1. *** Please download, test and VOTE before the *** vote closes EOD on Friday, November 28.*** http://people.apache.org/~phunt/zookeeper-3.0.1-candidate-1/ The only change to rc1 from rc0 is adding a missing apache license header to a source file: https://issues.apache.org/jira/browse/ZOOKEEPER-232 Should we release this? Patrick
[jira] Commented: (ZOOKEEPER-231) Quotas in zookeeper
[ https://issues.apache.org/jira/browse/ZOOKEEPER-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12650406#action_12650406 ] Mahadev konar commented on ZOOKEEPER-231: - here is a proposal for quotas -- The goal: - prevent run away processes or applications bringing down the service. - providing admins to look at usage and being able to monitor proactively What kind of quoata would we have - namespace quotas - bytes quota Proposal: - Reserve the node /zookeeper for zookeeper stats and zookeeper data management. - reserve /zookeeper/quota/ for quota related data structures The proposal is to have subtree based quotas for the number of bytes and number of nodes as well. The monitoring of quotas and stats should be availabe through the command port and through zookeeper itself via the /zookeeper node. The proposal is to have something like /zookeeper/quota/path/limits/size /zookeeper/quota/path/usage/size /zookeeper/quota/path/limits/count /zookeeper/quota/path/usage/count limits are the stored values that signify the limit for a subtree path and usage denote the actual usage of the subtree in terms of bytes or count or number of writes/reads. > Quotas in zookeeper > --- > > Key: ZOOKEEPER-231 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-231 > Project: Zookeeper > Issue Type: New Feature >Affects Versions: 3.0.0 >Reporter: Mahadev konar >Assignee: Mahadev konar > Fix For: 3.1.0 > > > creating quota's in zookeeper so that a runaway application does not bring > down the zookeeper cluster. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-69) ZooKeeper logo
[ https://issues.apache.org/jira/browse/ZOOKEEPER-69?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12650389#action_12650389 ] Mahadev konar commented on ZOOKEEPER-69: do we have to choose between the 4? > ZooKeeper logo > -- > > Key: ZOOKEEPER-69 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-69 > Project: Zookeeper > Issue Type: Wish > Components: documentation >Reporter: Flavio Paiva Junqueira >Assignee: Benjamin Reed >Priority: Minor > Fix For: 3.1.0 > > Attachments: pbzk.gif, zk_logo_use.png, zk_logo_use2.png, > zookeeper-sketch.jpg > > > I think we need a cool logo for the project. The ones I've seen so far are a > little lame, and that includes the one I've created for SourceForge. If > anyone on this list has an idea or knows of anyone with some art skills, > plese add a commento to this Jira. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-69) ZooKeeper logo
[ https://issues.apache.org/jira/browse/ZOOKEEPER-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flavio Paiva Junqueira updated ZOOKEEPER-69: Attachment: zookeeper-sketch.jpg Alternative version of the same character. > ZooKeeper logo > -- > > Key: ZOOKEEPER-69 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-69 > Project: Zookeeper > Issue Type: Wish > Components: documentation >Reporter: Flavio Paiva Junqueira >Assignee: Benjamin Reed >Priority: Minor > Fix For: 3.1.0 > > Attachments: pbzk.gif, zk_logo_use.png, zk_logo_use2.png, > zookeeper-sketch.jpg > > > I think we need a cool logo for the project. The ones I've seen so far are a > little lame, and that includes the one I've created for SourceForge. If > anyone on this list has an idea or knows of anyone with some art skills, > plese add a commento to this Jira. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-69) ZooKeeper logo
[ https://issues.apache.org/jira/browse/ZOOKEEPER-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Reed updated ZOOKEEPER-69: --- Status: Patch Available (was: Open) > ZooKeeper logo > -- > > Key: ZOOKEEPER-69 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-69 > Project: Zookeeper > Issue Type: Wish > Components: documentation >Reporter: Flavio Paiva Junqueira >Assignee: Benjamin Reed >Priority: Minor > Fix For: 3.1.0 > > Attachments: pbzk.gif, zk_logo_use.png, zk_logo_use2.png > > > I think we need a cool logo for the project. The ones I've seen so far are a > little lame, and that includes the one I've created for SourceForge. If > anyone on this list has an idea or knows of anyone with some art skills, > plese add a commento to this Jira. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-69) ZooKeeper logo
[ https://issues.apache.org/jira/browse/ZOOKEEPER-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Reed updated ZOOKEEPER-69: --- Attachment: pbzk.gif A Powered by ZooKeeper logo. > ZooKeeper logo > -- > > Key: ZOOKEEPER-69 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-69 > Project: Zookeeper > Issue Type: Wish > Components: documentation >Reporter: Flavio Paiva Junqueira >Assignee: Benjamin Reed >Priority: Minor > Fix For: 3.1.0 > > Attachments: pbzk.gif, zk_logo_use.png, zk_logo_use2.png > > > I think we need a cool logo for the project. The ones I've seen so far are a > little lame, and that includes the one I've created for SourceForge. If > anyone on this list has an idea or knows of anyone with some art skills, > plese add a commento to this Jira. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-69) ZooKeeper logo
[ https://issues.apache.org/jira/browse/ZOOKEEPER-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Reed updated ZOOKEEPER-69: --- Attachment: zk_logo_use2.png Simplified version of the logo. > ZooKeeper logo > -- > > Key: ZOOKEEPER-69 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-69 > Project: Zookeeper > Issue Type: Wish > Components: documentation >Reporter: Flavio Paiva Junqueira >Assignee: Benjamin Reed >Priority: Minor > Fix For: 3.1.0 > > Attachments: pbzk.gif, zk_logo_use.png, zk_logo_use2.png > > > I think we need a cool logo for the project. The ones I've seen so far are a > little lame, and that includes the one I've created for SourceForge. If > anyone on this list has an idea or knows of anyone with some art skills, > plese add a commento to this Jira. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-69) ZooKeeper logo
[ https://issues.apache.org/jira/browse/ZOOKEEPER-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Reed updated ZOOKEEPER-69: --- Attachment: zk_logo_use.png > ZooKeeper logo > -- > > Key: ZOOKEEPER-69 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-69 > Project: Zookeeper > Issue Type: Wish > Components: documentation >Reporter: Flavio Paiva Junqueira >Assignee: Benjamin Reed >Priority: Minor > Fix For: 3.1.0 > > Attachments: pbzk.gif, zk_logo_use.png, zk_logo_use2.png > > > I think we need a cool logo for the project. The ones I've seen so far are a > little lame, and that includes the one I've created for SourceForge. If > anyone on this list has an idea or knows of anyone with some art skills, > plese add a commento to this Jira. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-237) Add a Chroot request
[ https://issues.apache.org/jira/browse/ZOOKEEPER-237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12650369#action_12650369 ] Benjamin Reed commented on ZOOKEEPER-237: - If you bind a credential to a root, you end up tying yourself to a particular authorization scheme and id. If ACLs are used, you would not be able to circumvent the root. And by using an identifier not tied to a credential, you can support multiple credentials for a given root. For example, you may have /mySpace1, and you have some clients that are in a trusted cluster that "authenticate" with ip addresses and others that use stronger credentials. You may also have the converse problem where a given credential may have access to /mySpace1 and /yourSpace2, so the root would be ambiguous. > Add a Chroot request > > > Key: ZOOKEEPER-237 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-237 > Project: Zookeeper > Issue Type: New Feature >Reporter: Benjamin Reed >Priority: Minor > > 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.
[jira] Commented: (ZOOKEEPER-233) Create a slimer jar for clients to reduce thier disk footprint.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12650343#action_12650343 ] Patrick Hunt commented on ZOOKEEPER-233: +1 - update build.xml to generate a new zookeeper-client jar containing only the zk java files needed for a client (dont' modify the content of the existing zookeeper jar). > Create a slimer jar for clients to reduce thier disk footprint. > --- > > Key: ZOOKEEPER-233 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-233 > Project: Zookeeper > Issue Type: New Feature >Reporter: Hiram Chirino >Assignee: Patrick Hunt >Priority: Trivial > > Patrick request I open up this in issue in this [email > thread|http://n2.nabble.com/ActiveMQ-is-now-using-ZooKeeper-td1573272.html] -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (ZOOKEEPER-239) ZooKeeper System Tests
ZooKeeper System Tests -- Key: ZOOKEEPER-239 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-239 Project: Zookeeper Issue Type: Test Components: c client, java client Reporter: Benjamin Reed It would be nice to have real system tests. Our current Java system tests start everything in the same JVM. It would be nice to be able to start up the servers on different machines. The C tests have a system test with a script to start and stop the cluster. It would be good to extend the script and to make it used by the Java tests as well. If we can standardize on the script, we can have script options for different cluster shells from simple ssh to torque. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-28) Incompatible client and server list detection
[ https://issues.apache.org/jira/browse/ZOOKEEPER-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12650340#action_12650340 ] Benjamin Reed commented on ZOOKEEPER-28: I have been thinking about this more and I've realized that perhaps the easiest/best way to implement this would be to add a ListServers request to the clients. That way clients can do the validation themselves, and it can be done in a backwards compatible fashion. > Incompatible client and server list detection > - > > Key: ZOOKEEPER-28 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-28 > Project: Zookeeper > Issue Type: New Feature > Components: c client, java client, server >Reporter: Patrick Hunt > > Moved from SourceForge to Apache. > http://sourceforge.net/tracker/index.php?func=detail&aid=1937084&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] Commented: (ZOOKEEPER-237) Add a Chroot request
[ https://issues.apache.org/jira/browse/ZOOKEEPER-237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12650337#action_12650337 ] Patrick Hunt commented on ZOOKEEPER-237: I like the idea of being able to bind an application to a particular subtree. However this binding should be opaque to the client - the client should not be specifying (or circumventing) the root. The operator should map a credential to a root (ala aws s3) > Add a Chroot request > > > Key: ZOOKEEPER-237 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-237 > Project: Zookeeper > Issue Type: New Feature >Reporter: Benjamin Reed >Priority: Minor > > 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.
[jira] Created: (ZOOKEEPER-238) HostAuthenicationProvider should be removed
HostAuthenicationProvider should be removed --- Key: ZOOKEEPER-238 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-238 Project: Zookeeper Issue Type: Bug Reporter: Benjamin Reed I think the way the HostAuthenticationProvider is implemented could cause serious performance problems if DNS is slow or broken. The problem is that we need to do a reverse hostname resolution during connection establishment. I suggest it be removed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (ZOOKEEPER-237) Add a Chroot request
Add a Chroot request Key: ZOOKEEPER-237 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-237 Project: Zookeeper Issue Type: New Feature Reporter: Benjamin Reed Priority: Minor 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.
[jira] Created: (ZOOKEEPER-236) SSL Support for Atomic Broadcast protocol
SSL Support for Atomic Broadcast protocol - Key: ZOOKEEPER-236 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-236 Project: Zookeeper Issue Type: New Feature Reporter: Benjamin Reed Priority: Minor We should have the ability to use SSL to authenticate and encrypt the traffic between ZooKeeper servers. For the most part this is a very easy change. We would probably only want to support this for TCP based leader elections. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (ZOOKEEPER-235) SSL Support for clients
SSL Support for clients --- Key: ZOOKEEPER-235 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-235 Project: Zookeeper Issue Type: New Feature Reporter: Benjamin Reed ZooKeeper should be able to support SSL for ZooKeeper clients. As part of the implementation we should also add an X509AuthenticationProvider so that client side certifications can be used for authentication. The tricky part of the implementation will be integrating with the non-blocking NIO calls that we use. There are various web pages that describe how to do it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-235) SSL Support for clients
[ https://issues.apache.org/jira/browse/ZOOKEEPER-235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Reed updated ZOOKEEPER-235: Priority: Minor (was: Major) > SSL Support for clients > --- > > Key: ZOOKEEPER-235 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-235 > Project: Zookeeper > Issue Type: New Feature >Reporter: Benjamin Reed >Priority: Minor > > ZooKeeper should be able to support SSL for ZooKeeper clients. As part of the > implementation we should also add an X509AuthenticationProvider so that > client side certifications can be used for authentication. > The tricky part of the implementation will be integrating with the > non-blocking NIO calls that we use. There are various web pages that describe > how to do it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: ActiveMQ is now using ZooKeeper
done. On Mon, Nov 24, 2008 at 2:46 PM, Patrick Hunt <[EMAIL PROTECTED]> wrote: > That's great, very cool! > > Can you create ZOOKEEPER JIRAs for these items that you've identified? First > look it seems like we should be able to include these in 3.1.0, perhaps even > 3.0.2. > > Regards, > > Patrick > > Hiram Chirino wrote: >> >> FYI: >> >> ActiveMQ has now started using ZooKeeper to do master election of it's >> HA clusters. So zookeeper is now going to get included in every new >> ActiveMQ distro we cut. Which in turn this should mean that it will >> get included in every ServiceMix and Geronimo distro since they >> repackage ActiveMQ. >> >> More details at: >> http://cwiki.apache.org/confluence/display/ACTIVEMQ/KahaDB+Master+Slave >> >> So this might start bringing more folks/requirements to your project. >> For example it would be nice if: >> - You had a slim client only jar which we package with ActiveMQ to >> reduce our footprint, since we only use the client aspect of ZooKeeper >> - Make the sever more embeddable (for example eliminate using static >> vars to initialize the sever) so that it can be wrapped up in an OSGi >> bundle and deployed in ServiceMix. >> > -- Regards, Hiram Blog: http://hiramchirino.com Open Source SOA http://open.iona.com
[jira] Created: (ZOOKEEPER-234) Eliminate using statics to initialize the sever. Should allow server to be more embeddable in OSGi enviorments.
Eliminate using statics to initialize the sever. Should allow server to be
more embeddable in OSGi enviorments.
Key: ZOOKEEPER-234
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-234
Project: Zookeeper
Issue Type: Improvement
Reporter: Hiram Chirino
Assignee: Patrick Hunt
Patrick request I open up this in issue in this [email
thread|http://n2.nabble.com/ActiveMQ-is-now-using-ZooKeeper-td1573272.html]
The main culprit I've noticed is:
{code}
ServerStats.registerAsConcrete();
{code}
But there may be others.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (ZOOKEEPER-233) Create a slimer jar for clients to reduce thier disk footprint.
Create a slimer jar for clients to reduce thier disk footprint. --- Key: ZOOKEEPER-233 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-233 Project: Zookeeper Issue Type: New Feature Reporter: Hiram Chirino Assignee: Patrick Hunt Priority: Trivial Patrick request I open up this in issue in this [email thread|http://n2.nabble.com/ActiveMQ-is-now-using-ZooKeeper-td1573272.html] -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-232) testablezookeeper file is missing apache licence headers.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahadev konar updated ZOOKEEPER-232: Resolution: Fixed Hadoop Flags: [Reviewed] Status: Resolved (was: Patch Available) committed to revision 720288 in 3.0 and revision 720287 in trunk. > testablezookeeper file is missing apache licence headers. > - > > Key: ZOOKEEPER-232 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-232 > Project: Zookeeper > Issue Type: Bug >Reporter: Mahadev konar >Assignee: Mahadev konar >Priority: Blocker > Fix For: 3.0.1, 3.1.0 > > Attachments: ZOOKEEPER-232.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-232) testablezookeeper file is missing apache licence headers.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahadev konar updated ZOOKEEPER-232: Fix Version/s: 3.1.0 > testablezookeeper file is missing apache licence headers. > - > > Key: ZOOKEEPER-232 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-232 > Project: Zookeeper > Issue Type: Bug >Reporter: Mahadev konar >Assignee: Mahadev konar >Priority: Blocker > Fix For: 3.0.1, 3.1.0 > > Attachments: ZOOKEEPER-232.patch > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-232) testablezookeeper file is missing apache licence headers.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12650318#action_12650318 ] Patrick Hunt commented on ZOOKEEPER-232: +1, looks good. > testablezookeeper file is missing apache licence headers. > - > > Key: ZOOKEEPER-232 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-232 > Project: Zookeeper > Issue Type: Bug >Reporter: Mahadev konar >Assignee: Mahadev konar >Priority: Blocker > Fix For: 3.0.1 > > Attachments: ZOOKEEPER-232.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-232) testablezookeeper file is missing apache licence headers.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahadev konar updated ZOOKEEPER-232: Status: Patch Available (was: Open) > testablezookeeper file is missing apache licence headers. > - > > Key: ZOOKEEPER-232 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-232 > Project: Zookeeper > Issue Type: Bug >Reporter: Mahadev konar >Assignee: Mahadev konar >Priority: Blocker > Fix For: 3.0.1 > > Attachments: ZOOKEEPER-232.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-232) testablezookeeper file is missing apache licence headers.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahadev konar updated ZOOKEEPER-232: Attachment: ZOOKEEPER-232.patch this patch fixes the issue. > testablezookeeper file is missing apache licence headers. > - > > Key: ZOOKEEPER-232 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-232 > Project: Zookeeper > Issue Type: Bug >Reporter: Mahadev konar >Assignee: Mahadev konar >Priority: Blocker > Fix For: 3.0.1 > > Attachments: ZOOKEEPER-232.patch > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: ActiveMQ is now using ZooKeeper
That's great, very cool! Can you create ZOOKEEPER JIRAs for these items that you've identified? First look it seems like we should be able to include these in 3.1.0, perhaps even 3.0.2. Regards, Patrick Hiram Chirino wrote: FYI: ActiveMQ has now started using ZooKeeper to do master election of it's HA clusters. So zookeeper is now going to get included in every new ActiveMQ distro we cut. Which in turn this should mean that it will get included in every ServiceMix and Geronimo distro since they repackage ActiveMQ. More details at: http://cwiki.apache.org/confluence/display/ACTIVEMQ/KahaDB+Master+Slave So this might start bringing more folks/requirements to your project. For example it would be nice if: - You had a slim client only jar which we package with ActiveMQ to reduce our footprint, since we only use the client aspect of ZooKeeper - Make the sever more embeddable (for example eliminate using static vars to initialize the sever) so that it can be wrapped up in an OSGi bundle and deployed in ServiceMix.
[jira] Created: (ZOOKEEPER-232) testablezookeeper file is missing apache licence headers.
testablezookeeper file is missing apache licence headers. - Key: ZOOKEEPER-232 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-232 Project: Zookeeper Issue Type: Bug Reporter: Mahadev konar Assignee: Mahadev konar Priority: Blocker Fix For: 3.0.1 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
ActiveMQ is now using ZooKeeper
FYI: ActiveMQ has now started using ZooKeeper to do master election of it's HA clusters. So zookeeper is now going to get included in every new ActiveMQ distro we cut. Which in turn this should mean that it will get included in every ServiceMix and Geronimo distro since they repackage ActiveMQ. More details at: http://cwiki.apache.org/confluence/display/ACTIVEMQ/KahaDB+Master+Slave So this might start bringing more folks/requirements to your project. For example it would be nice if: - You had a slim client only jar which we package with ActiveMQ to reduce our footprint, since we only use the client aspect of ZooKeeper - Make the sever more embeddable (for example eliminate using static vars to initialize the sever) so that it can be wrapped up in an OSGi bundle and deployed in ServiceMix. -- Regards, Hiram Blog: http://hiramchirino.com Open Source SOA http://open.iona.com
[jira] Commented: (ZOOKEEPER-224) Deploy ZooKeeper 3.0.0 to a Maven Repository
[
https://issues.apache.org/jira/browse/ZOOKEEPER-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12650272#action_12650272
]
Hiram Chirino commented on ZOOKEEPER-224:
-
Q: How are the .sha1 files generated? What's the command?
A:
{code}
prompt> openssl dgst -md5 < inputfile
prompt> openssl dgst -sha1 < inputfile
{code}
Q: I update maven-metadata.xml and regenerate the md5/sha1?
A: yes. maven-metadata.xml is mainly used by the plugin download system maven
has. it will consult this file to see what the latest version of the artifact
is. So while it's not critical that the metadata is maintained, it is done for
all maven deployed artifacts so ideally it should be done.
Q: And also create a new 3.0.1 subdir at the same level as the 3.0.0 subdir?
A: Yes
Q: Should I include 3.0.0 as well or just 3.0.1?
A: Yes please. That way all your releases are available via Maven.
> Deploy ZooKeeper 3.0.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
>
> 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.
Re: [VOTE] Release ZooKeeper 3.0.1 (candidate 0)
+1 I'll check out the next build, but this one passed our unit tests and had a successful 24 hours in the Beta environment. Thanks, Stu -Original Message- From: "Patrick Hunt" <[EMAIL PROTECTED]> Sent: Monday, November 24, 2008 12:24am To: "Patrick Hunt" <[EMAIL PROTECTED]> Cc: zookeeper-dev@hadoop.apache.org Subject: Re: [VOTE] Release ZooKeeper 3.0.1 (candidate 0) -1 I noticed that src/java/test/org/apache/zookeeper/TestableZooKeeper.java is missing Apache license header. We'll have to add a header and put up a new rc for voting (tomorrow) Patrick Patrick Hunt wrote: > I've created a candidate build for ZooKeeper 3.0.1. > > *** Please download, test and VOTE before the > *** vote closes EOD on Monday, November 24.*** > > http://people.apache.org/~phunt/zookeeper-3.0.1-candidate-0/ > > Should we release this? > > Patrick > >
