[jira] Updated: (ZOOKEEPER-773) Log visualisation
[ https://issues.apache.org/jira/browse/ZOOKEEPER-773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-773: --- Status: Resolved (was: Patch Available) Hadoop Flags: [Reviewed] Resolution: Fixed +1, thanks Ivan, this looks to be a very useful tool! Log visualisation - Key: ZOOKEEPER-773 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-773 Project: Zookeeper Issue Type: Improvement Components: contrib Reporter: Ivan Kelly Assignee: Ivan Kelly Priority: Minor Fix For: 3.4.0 Attachments: test5.logs.tgz, ZOOKEEPER-773.binaries.tgz, ZOOKEEPER-773.diff Zkgraph is a log viewer for zookeeper. It can handle transaction logs and message logs. There are currently two view. a) Server view The server view shows the interactions between the different servers in an ensemble. The X axis represents time. * Exceptions show up as red dots. Hovering your mouse over them will give you more details of the exception * The colour of the line represents the election state of the server. - orange means LOOKING for leader - dark green means the server is the leader - light green means the server is following a leader - yellow means there isn't enough information to determine the state of the server. * The gray arrows denote election messages between servers. Pink dashed arrows are messages that were sent but never delivered. b) Session view The session view shows the lifetime of sessions on a server. Use the time filter to narrow down the view. Any more than about 2000 events will take a long time to view in your browser. The Y axis represents time in this case. Each line is a session. The black dots represent events on the session. You can click on the black dots for more details of the event. 2 - Compiling Running Run ant jar in src/contrib/zkgraph/. This will download all dependencies and compile all the zkgraph code. Once compilation has finished, you can run it the the zkgraph.sh script in src/contrib/zkgraph/bin. This will start and embedded web server on you machine. Navigate to http://localhost:8182/graph/main.html. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ZOOKEEPER-767) Submitting Demo/Recipe Shared / Exclusive Lock Code
[
https://issues.apache.org/jira/browse/ZOOKEEPER-767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12877131#action_12877131
]
Benjamin Reed commented on ZOOKEEPER-767:
-
1) just to make sure we are talking about the same thing. this is the code i'm
referring to:
{noformat}
// Check that we don't already have a lock...
if (currentExclusiveLock != null !isExpired(currentExclusiveLock)) {
// We have the exclusive lock! Remove newly made lock file and just
// return.
zooKeeper.delete(writeLock, -1);
return currentExclusiveLock;
}
{noformat}
2) no, i'm talking about when you go to get the shared lock, you first check to
see if you have a shared lock. shouldn't you check for both shared and
exclusive?
3) the problem is that connection loss and session expiration are different.
with connection loss you will get an exception, but your session can recover
and you can keep using it. for session expired you are right the EPHEMERAL will
go away. in the connection loss scenario you have a situation where you may
acquire a lock but not know it.
with regard to the question of current lock implementation in the repository.
i'm trying to understand the differences with that implementation and yours.
both follow the same recipe right? if the current lock implementation
implemented shared locks, would you have used that one? or is there something
more fundamental?
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, 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.
Fwd: RE: WORKSHOP ORGANIZER ZooKeeper
Fellow contributors, Yahoo is hosting a contributor workshop the day after the Hadoop Summit. The purpose of the workshops is to collectively discuss challenges, concerns and future ideas around ZooKeeper technologies. This will be held at Yahoo's Sunnyvale campus, all ZooKeeper contributors are welcome to attend. I was thinking of doing a half day with something like the following agenda: * intros * presentations ** phunt - status of zk, roadmap ** addl presentations * discussion, qa with committers/contributors, etc... If you would like to present please respond to this email with details. It's probably a good idea to keep the presentations down to 20-30 minutes max. I'd like to get back to Yahoo with an agenda soon so let me know asap. Patrick Original Message Subject: RE: WORKSHOP ORGANIZER ZooKeeper Date: Wed, 9 Jun 2010 10:52:27 -0700 From: Dekel Tankel de...@yahoo-inc.com To: Patrick Hunt ph...@apache.org Hi Patrick. We are setting up 3 meeting on the contributes meetup page for June 30th. It will be in the classrooms in building E on the SNV campus. I have the agenda for the core and Pig meetings, can you send me the zookeeper one as well (lunch will be available next to the classroom around 12). You can make it a half day or a full day, up to you. I'll setup the meeting with the classroom location once I hear back. I will also provide a conference number. -Original Message- From: Patrick Hunt [mailto:ph...@apache.org] Sent: Friday, June 04, 2010 11:53 AM To: hadoopcontribu...@yahoo-inc.com Cc: Owen O'Malley Subject: Re: WORKSHOP ORGANIZER ZooKeeper Are there any more details on this that you could share. I'd like to ramp up discussion on this in our contributor community, but I think that I should provide some detail as part of this. For example if I could confirm the location and time that we have available for our meeting. Will we have a conference bridge available to us? Conference phone? Thanks, Patrick On 03/29/2010 04:27 PM, Patrick Hunt wrote: The ZooKeeper team would like to have it's own workshop on the 30th. In our case we probably only need 2 hrs or so on that day. I will be the coordinator for our event, please let me know what I need to do. Thanks, Patrick
Re: Fwd: RE: WORKSHOP ORGANIZER ZooKeeper
i will be there. i would be glad to do a talk on bookkeeper/hedwig. ben On 06/09/2010 11:10 AM, Patrick Hunt wrote: Fellow contributors, Yahoo is hosting a contributor workshop the day after the Hadoop Summit. The purpose of the workshops is to collectively discuss challenges, concerns and future ideas around ZooKeeper technologies. This will be held at Yahoo's Sunnyvale campus, all ZooKeeper contributors are welcome to attend. I was thinking of doing a half day with something like the following agenda: * intros * presentations ** phunt - status of zk, roadmap **addl presentations * discussion, qa with committers/contributors, etc... If you would like to present please respond to this email with details. It's probably a good idea to keep the presentations down to 20-30 minutes max. I'd like to get back to Yahoo with an agenda soon so let me know asap. Patrick Original Message Subject: RE: WORKSHOP ORGANIZER ZooKeeper Date: Wed, 9 Jun 2010 10:52:27 -0700 From: Dekel Tankelde...@yahoo-inc.com To: Patrick Huntph...@apache.org Hi Patrick. We are setting up 3 meeting on the contributes meetup page for June 30th. It will be in the classrooms in building E on the SNV campus. I have the agenda for the core and Pig meetings, can you send me the zookeeper one as well (lunch will be available next to the classroom around 12). You can make it a half day or a full day, up to you. I'll setup the meeting with the classroom location once I hear back. I will also provide a conference number. -Original Message- From: Patrick Hunt [mailto:ph...@apache.org] Sent: Friday, June 04, 2010 11:53 AM To: hadoopcontribu...@yahoo-inc.com Cc: Owen O'Malley Subject: Re: WORKSHOP ORGANIZER ZooKeeper Are there any more details on this that you could share. I'd like to ramp up discussion on this in our contributor community, but I think that I should provide some detail as part of this. For example if I could confirm the location and time that we have available for our meeting. Will we have a conference bridge available to us? Conference phone? Thanks, Patrick On 03/29/2010 04:27 PM, Patrick Hunt wrote: The ZooKeeper team would like to have it's own workshop on the 30th. In our case we probably only need 2 hrs or so on that day. I will be the coordinator for our event, please let me know what I need to do. Thanks, Patrick
[jira] Commented: (ZOOKEEPER-740) zkpython leading to segfault on zookeeper
[ https://issues.apache.org/jira/browse/ZOOKEEPER-740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12877227#action_12877227 ] Henry Robinson commented on ZOOKEEPER-740: -- Mike - Great catch, thanks for figuring this out. I'm correct in saying that this doesn't prevent watchers from eventually being correctly freed, right? If so, then it would be great if you could submit this patch formally so that we can get it into trunk. See http://wiki.apache.org/hadoop/ZooKeeper/HowToContribute for details. Thanks, Henry zkpython leading to segfault on zookeeper - Key: ZOOKEEPER-740 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-740 Project: Zookeeper Issue Type: Bug Affects Versions: 3.3.0 Reporter: Federico Assignee: Henry Robinson Priority: Critical Fix For: 3.4.0 The program that we are implementing uses the python binding for zookeeper but sometimes it crash with segfault; here is the bt from gdb: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xad244b70 (LWP 28216)] 0x080611d5 in PyObject_Call (func=0x862fab0, arg=0x8837194, kw=0x0) at ../Objects/abstract.c:2488 2488../Objects/abstract.c: No such file or directory. in ../Objects/abstract.c (gdb) bt #0 0x080611d5 in PyObject_Call (func=0x862fab0, arg=0x8837194, kw=0x0) at ../Objects/abstract.c:2488 #1 0x080d6ef2 in PyEval_CallObjectWithKeywords (func=0x862fab0, arg=0x8837194, kw=0x0) at ../Python/ceval.c:3575 #2 0x080612a0 in PyObject_CallObject (o=0x862fab0, a=0x8837194) at ../Objects/abstract.c:2480 #3 0x0047af42 in watcher_dispatch (zzh=0x86174e0, type=-1, state=1, path=0x86337c8 , context=0x8588660) at src/c/zookeeper.c:314 #4 0x00496559 in do_foreach_watcher (zh=0x86174e0, type=-1, state=1, path=0x86337c8 , list=0xa5354140) at src/zk_hashtable.c:275 #5 deliverWatchers (zh=0x86174e0, type=-1, state=1, path=0x86337c8 , list=0xa5354140) at src/zk_hashtable.c:317 #6 0x0048ae3c in process_completions (zh=0x86174e0) at src/zookeeper.c:1766 #7 0x0049706b in do_completion (v=0x86174e0) at src/mt_adaptor.c:333 #8 0x0013380e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #9 0x002578de in clone () from /lib/tls/i686/cmov/libc.so.6 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
