Please get your gpg keys signed!

2010-06-25 Thread Thomas Koch
Hi,

I just wanted to package the new HBase version and since I've just recently 
read about a malicious software tarball for some Linux IRC server[1], I got 
back to the habbit of checking signatures. (Yes, I was lazy recently. I'm 
ashamed.)

But checking the signatures of apache software obviously is meaningless, since 
apache developers appears to not have their keys in the web-of-trust. From 
three signature files I had laying around on my hard disc, all three keys had 
zero signatures on the MIT keyserver:

30CD0996 2010-05-03 Michael Stack st...@duboce.net
68E327C1 2008-10-22 Patrick Hunt ph...@apache.org
FE045966 2009-10-13 Grant Ingersoll gsing...@apache.org

So please, when you've your next Hadoop / HBase / Lucene / Apache meetings, 
take your time for a keysigning party[2]. Or just have some snippet with your 
keys fingerprint in your wallet and hand it to every other geek you meet. (And 
make sure he asks you for your ID card to check your identity!) It's also nice 
to have your gpg fingerprint on your business cards!

[1] http://www.sophos.com/blogs/chetw/g/2010/06/12/linux-malware-rears-ugly-
head/
[2] http://en.wikipedia.org/wiki/Key_signing_party

Thank you!

Thomas Koch, http://www.koch.ro


[jira] Created: (ZOOKEEPER-793) Large-scale Pub/Sub System (C++ Client)

2010-06-25 Thread Ivan Kelly (JIRA)
Large-scale Pub/Sub System (C++ Client)
---

 Key: ZOOKEEPER-793
 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-793
 Project: Zookeeper
  Issue Type: Sub-task
Reporter: Ivan Kelly
Assignee: Ivan Kelly


Write a c++ client for hedwig

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Updated: (ZOOKEEPER-793) Large-scale Pub/Sub System (C++ Client)

2010-06-25 Thread Ivan Kelly (JIRA)

 [ 
https://issues.apache.org/jira/browse/ZOOKEEPER-793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ivan Kelly updated ZOOKEEPER-793:
-

Attachment: hedwig-cpp-0.1.tar.gz

First drop of C++ client

 Large-scale Pub/Sub System (C++ Client)
 ---

 Key: ZOOKEEPER-793
 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-793
 Project: Zookeeper
  Issue Type: Sub-task
Reporter: Ivan Kelly
Assignee: Ivan Kelly
 Attachments: hedwig-cpp-0.1.tar.gz


 Write a c++ client for hedwig

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Commented: (ZOOKEEPER-703) GSoC 2010: ZooKeeper DNS Server

2010-06-25 Thread Fred Emmott (JIRA)

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12882607#action_12882607
 ] 

Fred Emmott commented on ZOOKEEPER-703:
---

Quick-and-dirty code:

http://gitorious.org/zkdns/zkdns

No promises about reliability etc. We only use this to provide a convenience 
hostname for accessing the hbase master web interface (not depended on by any 
live services).

Can be used for any entry containing an ipv4 address, optionally followed by a 
port. Hostname format is /hbase/master - master.hbase.zk. We use CNAMEs to 
hook this into our existing hierarchy.

 GSoC 2010: ZooKeeper DNS Server
 ---

 Key: ZOOKEEPER-703
 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-703
 Project: Zookeeper
  Issue Type: Wish
Reporter: Henry Robinson

 ZooKeeper DNS Server
 Possible Mentor
 Henry Robinson (henry at apache dot org)
 Requirements
 Java or Python or C
 Description
 Although ZooKeeper is primarily used for co-ordination of distributed 
 processes, its consistency semantics means that it's a good candidate for 
 serving small (key,value) records as well. The Domain Name Service has 
 similar requirements, raising the interesting question of whether ZooKeeper 
 would be a capable DNS server for your local network. One intriguing 
 possibility is having versioned DNS records, such that known-good 
 configurations can be stored and rolled back to in the case of an issue. If 
 this versioning primitive proves to be useful, it's easy to imagine other 
 types of configuration that could be stored.
 This project would involve designing and building an RFC-1035 compliant DNS 
 server and performing a detailed performance study against an already 
 existant simple DNS server like tinydns.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



Re: Please get your gpg keys signed!

2010-06-25 Thread Torsten Curdt
 But checking the signatures of apache software obviously is meaningless, since
 apache developers appears to not have their keys in the web-of-trust

Many many do :)

 So please, when you've your next Hadoop / HBase / Lucene / Apache meetings,
 take your time for a keysigning party[2].

We should have done some key signing during the buzzwords conference.
For people in Berlin: I am happy to exchange keys to get them into the
web-of-trust.
Will certainly suggest something like that for our Apache Dinners.

cheers
--
Torsten


Re: Please get your gpg keys signed!

2010-06-25 Thread Patrick Hunt
Thomas, are you attending the summit? There are a number of contributor 
workshops the day after, all at (or around) the same location. If you 
feel strongly about this consider attending them, seems like great 
opportunity for a key signing party.

http://www.meetup.com/Hadoop-Contributors/calendar/13771414/
http://www.meetup.com/Hadoop-Contributors/calendar/13750403/
http://www.meetup.com/hbaseusergroup/calendar/13562846/
etc...

Here's some detail on WOT at apache:
http://www.apache.org/dev/release-signing.html#web-of-trust

Patrick

On 06/25/2010 02:29 AM, Thomas Koch wrote:

Hi,

I just wanted to package the new HBase version and since I've just recently
read about a malicious software tarball for some Linux IRC server[1], I got
back to the habbit of checking signatures. (Yes, I was lazy recently. I'm
ashamed.)

But checking the signatures of apache software obviously is meaningless, since
apache developers appears to not have their keys in the web-of-trust. From
three signature files I had laying around on my hard disc, all three keys had
zero signatures on the MIT keyserver:

30CD0996 2010-05-03 Michael Stackst...@duboce.net
68E327C1 2008-10-22 Patrick Huntph...@apache.org
FE045966 2009-10-13 Grant Ingersollgsing...@apache.org

So please, when you've your next Hadoop / HBase / Lucene / Apache meetings,
take your time for a keysigning party[2]. Or just have some snippet with your
keys fingerprint in your wallet and hand it to every other geek you meet. (And
make sure he asks you for your ID card to check your identity!) It's also nice
to have your gpg fingerprint on your business cards!

[1] http://www.sophos.com/blogs/chetw/g/2010/06/12/linux-malware-rears-ugly-
head/
[2] http://en.wikipedia.org/wiki/Key_signing_party

Thank you!

Thomas Koch, http://www.koch.ro


Re: Quorum tests improvement

2010-06-25 Thread Patrick Hunt
Sounds like a good idea to me, improving our ability to test quorum 
configurations would be great.


Patrick

On 06/23/2010 11:46 AM, Sergey Doroshenko wrote:

While incorporating tests for read-only mode, I found I don't like how
QuorumBase, the main utility for quorum testing, is made -- it has 5 fields
for 5 QuorumPeers, also 5 fields for ports, 5 fields for directories. In
general, it's very inflexible (you can't easily shutdown particular peer and
then bring up, etc) and hard-coded.

I think it would be nice to create a class which would setup 2n+1 peers, and
it would be possible to start/stop all peers / particular peer / n+1 peers
etc. And make QuorumBase particular case of this class with n=2.

What do you think?



[jira] Assigned: (ZOOKEEPER-792) zkpython memory leak

2010-06-25 Thread Patrick Hunt (JIRA)

 [ 
https://issues.apache.org/jira/browse/ZOOKEEPER-792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Patrick Hunt reassigned ZOOKEEPER-792:
--

Assignee: Lei Zhang

 zkpython memory leak
 

 Key: ZOOKEEPER-792
 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-792
 Project: Zookeeper
  Issue Type: Bug
  Components: contrib-bindings
Affects Versions: 3.3.1
 Environment: vmware workstation - guest OS:Linux python:2.4.3
Reporter: Lei Zhang
Assignee: Lei Zhang
 Fix For: 3.3.2, 3.4.0

 Attachments: ZOOKEEPER-792.patch


 We recently upgraded zookeeper from 3.2.1 to 3.3.1, now we are seeing less 
 client deadlock on session expiration, which is a definite plus!
 Unfortunately we are seeing memory leak that requires our zk clients to be 
 restarted every half-day. Valgrind result:
 ==8804== 25 (12 direct, 13 indirect) bytes in 1 blocks are definitely lost in 
 loss record 255 of 670
 ==8804==at 0x4021C42: calloc (vg_replace_malloc.c:418)
 ==8804==by 0x5047B42: parse_acls (zookeeper.c:369)
 ==8804==by 0x5047EF6: pyzoo_create (zookeeper.c:1009)
 ==8804==by 0x40786CC: PyCFunction_Call (in /usr/lib/libpython2.4.so.1.0)
 ==8804==by 0x40B31DC: PyEval_EvalFrame (in /usr/lib/libpython2.4.so.1.0)
 ==8804==by 0x40B4485: PyEval_EvalCodeEx (in /usr/lib/libpython2.4.so.1.0)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Updated: (ZOOKEEPER-712) Bookie recovery

2010-06-25 Thread Patrick Hunt (JIRA)

 [ 
https://issues.apache.org/jira/browse/ZOOKEEPER-712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Patrick Hunt updated ZOOKEEPER-712:
---

Fix Version/s: 3.4.0

 Bookie recovery
 ---

 Key: ZOOKEEPER-712
 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-712
 Project: Zookeeper
  Issue Type: New Feature
  Components: contrib-bookkeeper
Reporter: Flavio Paiva Junqueira
Assignee: Erwin Tam
 Fix For: 3.4.0

 Attachments: ZOOKEEPER-712.patch


 Recover the ledger fragments of a bookie once it crashes.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Updated: (ZOOKEEPER-744) Add monitoring four-letter word

2010-06-25 Thread Patrick Hunt (JIRA)

 [ 
https://issues.apache.org/jira/browse/ZOOKEEPER-744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Patrick Hunt updated ZOOKEEPER-744:
---

Status: Patch Available  (was: Open)

 Add monitoring four-letter word
 ---

 Key: ZOOKEEPER-744
 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-744
 Project: Zookeeper
  Issue Type: New Feature
  Components: server
Affects Versions: 3.4.0
Reporter: Travis Crawford
Assignee: Andrei Savu
 Fix For: 3.4.0

 Attachments: zk-ganglia.png, ZOOKEEPER-744.patch, 
 ZOOKEEPER-744.patch, ZOOKEEPER-744.patch, ZOOKEEPER-744.patch


 Filing a feature request based on a zookeeper-user discussion.
 Zookeeper should have a new four-letter word that returns key-value pairs 
 appropriate for importing to a monitoring system (such as Ganglia which has a 
 large installed base)
 This command should initially export the following:
 (a) Count of instances in the ensemble.
 (b) Count of up-to-date instances in the ensemble.
 But be designed such that in the future additional data can be added. For 
 example, the output could define the statistic in a comment, then print a key 
 space character value line:
 
 # Total number of instances in the ensemble
 zk_ensemble_instances_total 5
 # Number of instances currently participating in the quorum.
 zk_ensemble_instances_active 4
 
 From the mailing list:
 
 Date: Mon, 19 Apr 2010 12:10:44 -0700
 From: Patrick Hunt ph...@apache.org
 To: zookeeper-u...@hadoop.apache.org
 Subject: Re: Recovery issue - how to debug?
 On 04/19/2010 11:55 AM, Travis Crawford wrote:
  It would be a lot easier from the operations perspective if the leader
  explicitly published some health stats:
 
  (a) Count of instances in the ensemble.
  (b) Count of up-to-date instances in the ensemble.
 
  This would greatly simplify monitoring  alerting - when an instance
  falls behind one could configure their monitoring system to let
  someone know and take a look at the logs.
 That's a great idea. Please enter a JIRA for this - a new 4 letter word 
 and JMX support. It would also be a great starter project for someone 
 interested in becoming more familiar with the server code.
 Patrick
 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Updated: (ZOOKEEPER-744) Add monitoring four-letter word

2010-06-25 Thread Patrick Hunt (JIRA)

 [ 
https://issues.apache.org/jira/browse/ZOOKEEPER-744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Patrick Hunt updated ZOOKEEPER-744:
---

Attachment: ZOOKEEPER-744.patch

Updated patch to fix indentation.

Andrei, please update your editor (eclipse?) to use spaces only, no tabs for 
indentation.


 Add monitoring four-letter word
 ---

 Key: ZOOKEEPER-744
 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-744
 Project: Zookeeper
  Issue Type: New Feature
  Components: server
Affects Versions: 3.4.0
Reporter: Travis Crawford
Assignee: Andrei Savu
 Fix For: 3.4.0

 Attachments: zk-ganglia.png, ZOOKEEPER-744.patch, 
 ZOOKEEPER-744.patch, ZOOKEEPER-744.patch, ZOOKEEPER-744.patch


 Filing a feature request based on a zookeeper-user discussion.
 Zookeeper should have a new four-letter word that returns key-value pairs 
 appropriate for importing to a monitoring system (such as Ganglia which has a 
 large installed base)
 This command should initially export the following:
 (a) Count of instances in the ensemble.
 (b) Count of up-to-date instances in the ensemble.
 But be designed such that in the future additional data can be added. For 
 example, the output could define the statistic in a comment, then print a key 
 space character value line:
 
 # Total number of instances in the ensemble
 zk_ensemble_instances_total 5
 # Number of instances currently participating in the quorum.
 zk_ensemble_instances_active 4
 
 From the mailing list:
 
 Date: Mon, 19 Apr 2010 12:10:44 -0700
 From: Patrick Hunt ph...@apache.org
 To: zookeeper-u...@hadoop.apache.org
 Subject: Re: Recovery issue - how to debug?
 On 04/19/2010 11:55 AM, Travis Crawford wrote:
  It would be a lot easier from the operations perspective if the leader
  explicitly published some health stats:
 
  (a) Count of instances in the ensemble.
  (b) Count of up-to-date instances in the ensemble.
 
  This would greatly simplify monitoring  alerting - when an instance
  falls behind one could configure their monitoring system to let
  someone know and take a look at the logs.
 That's a great idea. Please enter a JIRA for this - a new 4 letter word 
 and JMX support. It would also be a great starter project for someone 
 interested in becoming more familiar with the server code.
 Patrick
 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Updated: (ZOOKEEPER-744) Add monitoring four-letter word

2010-06-25 Thread Patrick Hunt (JIRA)

 [ 
https://issues.apache.org/jira/browse/ZOOKEEPER-744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Patrick Hunt updated ZOOKEEPER-744:
---

Status: Open  (was: Patch Available)

 Add monitoring four-letter word
 ---

 Key: ZOOKEEPER-744
 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-744
 Project: Zookeeper
  Issue Type: New Feature
  Components: server
Affects Versions: 3.4.0
Reporter: Travis Crawford
Assignee: Andrei Savu
 Fix For: 3.4.0

 Attachments: zk-ganglia.png, ZOOKEEPER-744.patch, 
 ZOOKEEPER-744.patch, ZOOKEEPER-744.patch, ZOOKEEPER-744.patch


 Filing a feature request based on a zookeeper-user discussion.
 Zookeeper should have a new four-letter word that returns key-value pairs 
 appropriate for importing to a monitoring system (such as Ganglia which has a 
 large installed base)
 This command should initially export the following:
 (a) Count of instances in the ensemble.
 (b) Count of up-to-date instances in the ensemble.
 But be designed such that in the future additional data can be added. For 
 example, the output could define the statistic in a comment, then print a key 
 space character value line:
 
 # Total number of instances in the ensemble
 zk_ensemble_instances_total 5
 # Number of instances currently participating in the quorum.
 zk_ensemble_instances_active 4
 
 From the mailing list:
 
 Date: Mon, 19 Apr 2010 12:10:44 -0700
 From: Patrick Hunt ph...@apache.org
 To: zookeeper-u...@hadoop.apache.org
 Subject: Re: Recovery issue - how to debug?
 On 04/19/2010 11:55 AM, Travis Crawford wrote:
  It would be a lot easier from the operations perspective if the leader
  explicitly published some health stats:
 
  (a) Count of instances in the ensemble.
  (b) Count of up-to-date instances in the ensemble.
 
  This would greatly simplify monitoring  alerting - when an instance
  falls behind one could configure their monitoring system to let
  someone know and take a look at the logs.
 That's a great idea. Please enter a JIRA for this - a new 4 letter word 
 and JMX support. It would also be a great starter project for someone 
 interested in becoming more familiar with the server code.
 Patrick
 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Updated: (ZOOKEEPER-788) Add server id to message logs

2010-06-25 Thread Patrick Hunt (JIRA)

 [ 
https://issues.apache.org/jira/browse/ZOOKEEPER-788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Patrick Hunt updated ZOOKEEPER-788:
---

  Status: Resolved  (was: Patch Available)
Hadoop Flags: [Reviewed]
  Resolution: Fixed

Thanks Ivan!


 Add server id to message logs
 -

 Key: ZOOKEEPER-788
 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-788
 Project: Zookeeper
  Issue Type: Improvement
  Components: contrib
Affects Versions: 3.3.1
Reporter: Ivan Kelly
Assignee: Ivan Kelly
Priority: Trivial
 Fix For: 3.4.0

 Attachments: ZOOKEEPER-778.patch


 As discussed on IRC. The log visualisation needs some way of determining 
 which server made which log. If the log segment is taken for a time period 
 where no elections take place, there is no way to determine the id of 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-789) Improve FLE log messages

2010-06-25 Thread Patrick Hunt (JIRA)

 [ 
https://issues.apache.org/jira/browse/ZOOKEEPER-789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Patrick Hunt updated ZOOKEEPER-789:
---

Status: Open  (was: Patch Available)

Flavio can you resubmit with using tabs for indentation? (good to update your 
editor to only use spaces, eclipse?) Thanks.


 Improve FLE log messages
 

 Key: ZOOKEEPER-789
 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-789
 Project: Zookeeper
  Issue Type: Improvement
Affects Versions: 3.3.1
Reporter: Flavio Paiva Junqueira
Assignee: Flavio Paiva Junqueira
 Fix For: 3.3.2, 3.4.0

 Attachments: ZOOKEEPER-789.patch


 Notification messages are quite important to determine what is going with 
 leader election. The main idea of this improvement is name the fields we 
 output in notification log messages.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Commented: (ZOOKEEPER-744) Add monitoring four-letter word

2010-06-25 Thread Hadoop QA (JIRA)

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12882736#action_12882736
 ] 

Hadoop QA commented on ZOOKEEPER-744:
-

-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12448091/ZOOKEEPER-744.patch
  against trunk revision 958096.

+1 @author.  The patch does not contain any @author tags.

+1 tests included.  The patch appears to include 12 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 failed 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/121/testReport/
Findbugs warnings: 
http://hudson.zones.apache.org/hudson/job/Zookeeper-Patch-h1.grid.sp2.yahoo.net/121/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output: 
http://hudson.zones.apache.org/hudson/job/Zookeeper-Patch-h1.grid.sp2.yahoo.net/121/console

This message is automatically generated.

 Add monitoring four-letter word
 ---

 Key: ZOOKEEPER-744
 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-744
 Project: Zookeeper
  Issue Type: New Feature
  Components: server
Affects Versions: 3.4.0
Reporter: Travis Crawford
Assignee: Andrei Savu
 Fix For: 3.4.0

 Attachments: zk-ganglia.png, ZOOKEEPER-744.patch, 
 ZOOKEEPER-744.patch, ZOOKEEPER-744.patch, ZOOKEEPER-744.patch


 Filing a feature request based on a zookeeper-user discussion.
 Zookeeper should have a new four-letter word that returns key-value pairs 
 appropriate for importing to a monitoring system (such as Ganglia which has a 
 large installed base)
 This command should initially export the following:
 (a) Count of instances in the ensemble.
 (b) Count of up-to-date instances in the ensemble.
 But be designed such that in the future additional data can be added. For 
 example, the output could define the statistic in a comment, then print a key 
 space character value line:
 
 # Total number of instances in the ensemble
 zk_ensemble_instances_total 5
 # Number of instances currently participating in the quorum.
 zk_ensemble_instances_active 4
 
 From the mailing list:
 
 Date: Mon, 19 Apr 2010 12:10:44 -0700
 From: Patrick Hunt ph...@apache.org
 To: zookeeper-u...@hadoop.apache.org
 Subject: Re: Recovery issue - how to debug?
 On 04/19/2010 11:55 AM, Travis Crawford wrote:
  It would be a lot easier from the operations perspective if the leader
  explicitly published some health stats:
 
  (a) Count of instances in the ensemble.
  (b) Count of up-to-date instances in the ensemble.
 
  This would greatly simplify monitoring  alerting - when an instance
  falls behind one could configure their monitoring system to let
  someone know and take a look at the logs.
 That's a great idea. Please enter a JIRA for this - a new 4 letter word 
 and JMX support. It would also be a great starter project for someone 
 interested in becoming more familiar with the server code.
 Patrick
 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Updated: (ZOOKEEPER-744) Add monitoring four-letter word

2010-06-25 Thread Patrick Hunt (JIRA)

 [ 
https://issues.apache.org/jira/browse/ZOOKEEPER-744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Patrick Hunt updated ZOOKEEPER-744:
---

Status: Open  (was: Patch Available)

 Add monitoring four-letter word
 ---

 Key: ZOOKEEPER-744
 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-744
 Project: Zookeeper
  Issue Type: New Feature
  Components: server
Affects Versions: 3.4.0
Reporter: Travis Crawford
Assignee: Andrei Savu
 Fix For: 3.4.0

 Attachments: zk-ganglia.png, ZOOKEEPER-744.patch, 
 ZOOKEEPER-744.patch, ZOOKEEPER-744.patch, ZOOKEEPER-744.patch


 Filing a feature request based on a zookeeper-user discussion.
 Zookeeper should have a new four-letter word that returns key-value pairs 
 appropriate for importing to a monitoring system (such as Ganglia which has a 
 large installed base)
 This command should initially export the following:
 (a) Count of instances in the ensemble.
 (b) Count of up-to-date instances in the ensemble.
 But be designed such that in the future additional data can be added. For 
 example, the output could define the statistic in a comment, then print a key 
 space character value line:
 
 # Total number of instances in the ensemble
 zk_ensemble_instances_total 5
 # Number of instances currently participating in the quorum.
 zk_ensemble_instances_active 4
 
 From the mailing list:
 
 Date: Mon, 19 Apr 2010 12:10:44 -0700
 From: Patrick Hunt ph...@apache.org
 To: zookeeper-u...@hadoop.apache.org
 Subject: Re: Recovery issue - how to debug?
 On 04/19/2010 11:55 AM, Travis Crawford wrote:
  It would be a lot easier from the operations perspective if the leader
  explicitly published some health stats:
 
  (a) Count of instances in the ensemble.
  (b) Count of up-to-date instances in the ensemble.
 
  This would greatly simplify monitoring  alerting - when an instance
  falls behind one could configure their monitoring system to let
  someone know and take a look at the logs.
 That's a great idea. Please enter a JIRA for this - a new 4 letter word 
 and JMX support. It would also be a great starter project for someone 
 interested in becoming more familiar with the server code.
 Patrick
 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Updated: (ZOOKEEPER-744) Add monitoring four-letter word

2010-06-25 Thread Patrick Hunt (JIRA)

 [ 
https://issues.apache.org/jira/browse/ZOOKEEPER-744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Patrick Hunt updated ZOOKEEPER-744:
---

Status: Patch Available  (was: Open)

 Add monitoring four-letter word
 ---

 Key: ZOOKEEPER-744
 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-744
 Project: Zookeeper
  Issue Type: New Feature
  Components: server
Affects Versions: 3.4.0
Reporter: Travis Crawford
Assignee: Andrei Savu
 Fix For: 3.4.0

 Attachments: zk-ganglia.png, ZOOKEEPER-744.patch, 
 ZOOKEEPER-744.patch, ZOOKEEPER-744.patch, ZOOKEEPER-744.patch


 Filing a feature request based on a zookeeper-user discussion.
 Zookeeper should have a new four-letter word that returns key-value pairs 
 appropriate for importing to a monitoring system (such as Ganglia which has a 
 large installed base)
 This command should initially export the following:
 (a) Count of instances in the ensemble.
 (b) Count of up-to-date instances in the ensemble.
 But be designed such that in the future additional data can be added. For 
 example, the output could define the statistic in a comment, then print a key 
 space character value line:
 
 # Total number of instances in the ensemble
 zk_ensemble_instances_total 5
 # Number of instances currently participating in the quorum.
 zk_ensemble_instances_active 4
 
 From the mailing list:
 
 Date: Mon, 19 Apr 2010 12:10:44 -0700
 From: Patrick Hunt ph...@apache.org
 To: zookeeper-u...@hadoop.apache.org
 Subject: Re: Recovery issue - how to debug?
 On 04/19/2010 11:55 AM, Travis Crawford wrote:
  It would be a lot easier from the operations perspective if the leader
  explicitly published some health stats:
 
  (a) Count of instances in the ensemble.
  (b) Count of up-to-date instances in the ensemble.
 
  This would greatly simplify monitoring  alerting - when an instance
  falls behind one could configure their monitoring system to let
  someone know and take a look at the logs.
 That's a great idea. Please enter a JIRA for this - a new 4 letter word 
 and JMX support. It would also be a great starter project for someone 
 interested in becoming more familiar with the server code.
 Patrick
 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Commented: (ZOOKEEPER-744) Add monitoring four-letter word

2010-06-25 Thread Hadoop QA (JIRA)

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12882759#action_12882759
 ] 

Hadoop QA commented on ZOOKEEPER-744:
-

+1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12448091/ZOOKEEPER-744.patch
  against trunk revision 958096.

+1 @author.  The patch does not contain any @author tags.

+1 tests included.  The patch appears to include 12 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/122/testReport/
Findbugs warnings: 
http://hudson.zones.apache.org/hudson/job/Zookeeper-Patch-h1.grid.sp2.yahoo.net/122/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output: 
http://hudson.zones.apache.org/hudson/job/Zookeeper-Patch-h1.grid.sp2.yahoo.net/122/console

This message is automatically generated.

 Add monitoring four-letter word
 ---

 Key: ZOOKEEPER-744
 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-744
 Project: Zookeeper
  Issue Type: New Feature
  Components: server
Affects Versions: 3.4.0
Reporter: Travis Crawford
Assignee: Andrei Savu
 Fix For: 3.4.0

 Attachments: zk-ganglia.png, ZOOKEEPER-744.patch, 
 ZOOKEEPER-744.patch, ZOOKEEPER-744.patch, ZOOKEEPER-744.patch


 Filing a feature request based on a zookeeper-user discussion.
 Zookeeper should have a new four-letter word that returns key-value pairs 
 appropriate for importing to a monitoring system (such as Ganglia which has a 
 large installed base)
 This command should initially export the following:
 (a) Count of instances in the ensemble.
 (b) Count of up-to-date instances in the ensemble.
 But be designed such that in the future additional data can be added. For 
 example, the output could define the statistic in a comment, then print a key 
 space character value line:
 
 # Total number of instances in the ensemble
 zk_ensemble_instances_total 5
 # Number of instances currently participating in the quorum.
 zk_ensemble_instances_active 4
 
 From the mailing list:
 
 Date: Mon, 19 Apr 2010 12:10:44 -0700
 From: Patrick Hunt ph...@apache.org
 To: zookeeper-u...@hadoop.apache.org
 Subject: Re: Recovery issue - how to debug?
 On 04/19/2010 11:55 AM, Travis Crawford wrote:
  It would be a lot easier from the operations perspective if the leader
  explicitly published some health stats:
 
  (a) Count of instances in the ensemble.
  (b) Count of up-to-date instances in the ensemble.
 
  This would greatly simplify monitoring  alerting - when an instance
  falls behind one could configure their monitoring system to let
  someone know and take a look at the logs.
 That's a great idea. Please enter a JIRA for this - a new 4 letter word 
 and JMX support. It would also be a great starter project for someone 
 interested in becoming more familiar with the server code.
 Patrick
 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Created: (ZOOKEEPER-794) Callbacks are not invoked when the client is closed

2010-06-25 Thread Alexis Midon (JIRA)
Callbacks are not invoked when the client is closed
---

 Key: ZOOKEEPER-794
 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-794
 Project: Zookeeper
  Issue Type: Bug
  Components: java client
Affects Versions: 3.3.1
Reporter: Alexis Midon



I noticed that ZooKeeper has different behaviors when calling synchronous or 
asynchronous actions on a closed ZooKeeper client.
Actually a synchronous call will throw a session expired exception while an 
asynchronous call will do nothing. No exception, no callback invocation.

Actually, even if the EventThread receives the Packet with the session expired 
err code, the packet is never processed since the thread has been killed by the 
ventOfDeath. So the call back is not invoked.



-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Updated: (ZOOKEEPER-794) Callbacks are not invoked when the client is closed

2010-06-25 Thread Alexis Midon (JIRA)

 [ 
https://issues.apache.org/jira/browse/ZOOKEEPER-794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexis Midon updated ZOOKEEPER-794:
---

Status: Patch Available  (was: Open)

The patch is to not queue the event when the event thread has been killed and 
process it on the spot.

 Callbacks are not invoked when the client is closed
 ---

 Key: ZOOKEEPER-794
 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-794
 Project: Zookeeper
  Issue Type: Bug
  Components: java client
Affects Versions: 3.3.1
Reporter: Alexis Midon
 Attachments: ZOOKEEPER-794.patch.txt


 I noticed that ZooKeeper has different behaviors when calling synchronous or 
 asynchronous actions on a closed ZooKeeper client.
 Actually a synchronous call will throw a session expired exception while an 
 asynchronous call will do nothing. No exception, no callback invocation.
 Actually, even if the EventThread receives the Packet with the session 
 expired err code, the packet is never processed since the thread has been 
 killed by the ventOfDeath. So the call back is not invoked.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.



[jira] Commented: (ZOOKEEPER-794) Callbacks are not invoked when the client is closed

2010-06-25 Thread Hadoop QA (JIRA)

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12882802#action_12882802
 ] 

Hadoop QA commented on ZOOKEEPER-794:
-

-1 overall.  Here are the results of testing the latest attachment 
  
http://issues.apache.org/jira/secure/attachment/12448116/ZOOKEEPER-794.patch.txt
  against trunk revision 958096.

+1 @author.  The patch does not contain any @author tags.

-1 tests included.  The patch doesn't appear to include any new or modified 
tests.
Please justify why no tests are needed for this patch.

-1 patch.  The patch command could not apply the patch.

Console output: 
http://hudson.zones.apache.org/hudson/job/Zookeeper-Patch-h1.grid.sp2.yahoo.net/123/console

This message is automatically generated.

 Callbacks are not invoked when the client is closed
 ---

 Key: ZOOKEEPER-794
 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-794
 Project: Zookeeper
  Issue Type: Bug
  Components: java client
Affects Versions: 3.3.1
Reporter: Alexis Midon
 Attachments: ZOOKEEPER-794.patch.txt


 I noticed that ZooKeeper has different behaviors when calling synchronous or 
 asynchronous actions on a closed ZooKeeper client.
 Actually a synchronous call will throw a session expired exception while an 
 asynchronous call will do nothing. No exception, no callback invocation.
 Actually, even if the EventThread receives the Packet with the session 
 expired err code, the packet is never processed since the thread has been 
 killed by the ventOfDeath. So the call back is not invoked.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.