[jira] Updated: (ZOOKEEPER-227) gcc warning from recordio.h

[ https://issues.apache.org/jira/browse/ZOOKEEPER-227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-227: --- Fix Version/s: 3.0.1 let's try to get this one into 3.0.1 > gcc warning from recordio.h >

[jira] Updated: (ZOOKEEPER-64) We should log system env information when intializing client/server

[ https://issues.apache.org/jira/browse/ZOOKEEPER-64?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Reed updated ZOOKEEPER-64: --- Hadoop Flags: [Reviewed] +1 Excellent. > We should log system env information when intiali

[jira] Updated: (ZOOKEEPER-208) Zookeeper C client uses API that are not thread safe, causing crashes when multiple instances are active

[ https://issues.apache.org/jira/browse/ZOOKEEPER-208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Reed updated ZOOKEEPER-208: Attachment: ZOOKEEPER-208.patch Updated the tests to not look for usage of gethostbyname

[jira] Updated: (ZOOKEEPER-208) Zookeeper C client uses API that are not thread safe, causing crashes when multiple instances are active

[ https://issues.apache.org/jira/browse/ZOOKEEPER-208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Reed updated ZOOKEEPER-208: Status: Patch Available (was: Open) > Zookeeper C client uses API that are not thread s

[jira] Updated: (ZOOKEEPER-204) SetWatches needs to be the first message after auth messages to the server

[ https://issues.apache.org/jira/browse/ZOOKEEPER-204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahadev konar updated ZOOKEEPER-204: Attachment: ZOOKEEPER-204.patch made a few changes regarding logging and formatting

[jira] Updated: (ZOOKEEPER-211) Not all Mock tests are working

[ https://issues.apache.org/jira/browse/ZOOKEEPER-211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-211: --- Resolution: Fixed Hadoop Flags: [Reviewed] Status: Resolved (was: Patch Av

[jira] Updated: (ZOOKEEPER-208) Zookeeper C client uses API that are not thread safe, causing crashes when multiple instances are active

[ https://issues.apache.org/jira/browse/ZOOKEEPER-208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-208: --- Status: Open (was: Patch Available) Cancelling the patch: the c unit tests are failing (u

[jira] Updated: (ZOOKEEPER-226) exists calls fails on server if node has null data

[ https://issues.apache.org/jira/browse/ZOOKEEPER-226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahadev konar updated ZOOKEEPER-226: Resolution: Fixed Status: Resolved (was: Patch Available) committed to 718799 i

[jira] Updated: (ZOOKEEPER-204) SetWatches needs to be the first message after auth messages to the server

[ https://issues.apache.org/jira/browse/ZOOKEEPER-204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Reed updated ZOOKEEPER-204: Attachment: ZOOKEEPER-204.patch Good catch Flavio. Uploaded a fixed version. > SetWatch

[jira] Updated: (ZOOKEEPER-206) documentation tab should contain the version number (and other small site changes)

[ https://issues.apache.org/jira/browse/ZOOKEEPER-206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahadev konar updated ZOOKEEPER-206: Resolution: Fixed Status: Resolved (was: Patch Available) committed to revision

[jira] Updated: (ZOOKEEPER-208) Zookeeper C client uses API that are not thread safe, causing crashes when multiple instances are active

[ https://issues.apache.org/jira/browse/ZOOKEEPER-208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Reed updated ZOOKEEPER-208: Fix Version/s: 3.0.1 > Zookeeper C client uses API that are not thread safe, causing cra

[jira] Updated: (ZOOKEEPER-208) Zookeeper C client uses API that are not thread safe, causing crashes when multiple instances are active

[ https://issues.apache.org/jira/browse/ZOOKEEPER-208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Reed updated ZOOKEEPER-208: Hadoop Flags: [Reviewed] +1 great work. We should include this in 3.0.1 > Zookeeper C c

[jira] Updated: (ZOOKEEPER-226) exists calls fails on server if node has null data

[ https://issues.apache.org/jira/browse/ZOOKEEPER-226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Reed updated ZOOKEEPER-226: Hadoop Flags: [Reviewed] +1 Ready to commit > exists calls fails on server if node has

[jira] Updated: (ZOOKEEPER-206) documentation tab should contain the version number (and other small site changes)

[ https://issues.apache.org/jira/browse/ZOOKEEPER-206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahadev konar updated ZOOKEEPER-206: Hadoop Flags: [Reviewed] +1 for the patch... > documentation tab should contain the v

[jira] Commented: (ZOOKEEPER-206) documentation tab should contain the version number (and other small site changes)

[ https://issues.apache.org/jira/browse/ZOOKEEPER-206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12648804#action_12648804 ] Benjamin Reed commented on ZOOKEEPER-206: - +1 > documentation tab should conta

[jira] Commented: (ZOOKEEPER-221) log message in ZkWatchManager.materialize missing conditional

[ https://issues.apache.org/jira/browse/ZOOKEEPER-221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12648802#action_12648802 ] Mahadev konar commented on ZOOKEEPER-221: - Looks like ZOOKEEPER-204 has the fix

[jira] Updated: (ZOOKEEPER-218) error in barrier recipe example code

[ https://issues.apache.org/jira/browse/ZOOKEEPER-218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahadev konar updated ZOOKEEPER-218: Resolution: Fixed Status: Resolved (was: Patch Available) committed to revision

[jira] Updated: (ZOOKEEPER-218) error in barrier recipe example code

[ https://issues.apache.org/jira/browse/ZOOKEEPER-218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahadev konar updated ZOOKEEPER-218: Hadoop Flags: [Reviewed] +1 for the patch... > error in barrier recipe example code >

[jira] Updated: (ZOOKEEPER-226) exists calls fails on server if node has null data

[ https://issues.apache.org/jira/browse/ZOOKEEPER-226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahadev konar updated ZOOKEEPER-226: Status: Patch Available (was: Open) > exists calls fails on server if node has null dat

[jira] Updated: (ZOOKEEPER-226) exists calls fails on server if node has null data

[ https://issues.apache.org/jira/browse/ZOOKEEPER-226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahadev konar updated ZOOKEEPER-226: Attachment: ZOOKEEPER-226.patch this patch fixes the issue and also adds a test. > exis

[jira] Created: (ZOOKEEPER-229) improve documentation regarding user's responsibility to cleanup datadir (snaps/logs)

improve documentation regarding user's responsibility to cleanup datadir (snaps/logs) - Key: ZOOKEEPER-229 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-229 Pr

[jira] Issue Comment Edited: (ZOOKEEPER-208) Zookeeper C client uses API that are not thread safe, causing crashes when multiple instances are active

[ https://issues.apache.org/jira/browse/ZOOKEEPER-208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12648757#action_12648757 ] phunt edited comment on ZOOKEEPER-208 at 11/18/08 1:18 PM: ---

[jira] Updated: (ZOOKEEPER-208) Zookeeper C client uses API that are not thread safe, causing crashes when multiple instances are active

[ https://issues.apache.org/jira/browse/ZOOKEEPER-208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-208: --- Status: Patch Available (was: Open) Great. Thanks much Austin! I'm marking this as "patc

[jira] Commented: (ZOOKEEPER-208) Zookeeper C client uses API that are not thread safe, causing crashes when multiple instances are active

[ https://issues.apache.org/jira/browse/ZOOKEEPER-208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12648756#action_12648756 ] Austin Shoemaker commented on ZOOKEEPER-208: Chris, thanks for modifying my

[jira] Updated: (ZOOKEEPER-208) Zookeeper C client uses API that are not thread safe, causing crashes when multiple instances are active

[ https://issues.apache.org/jira/browse/ZOOKEEPER-208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Austin Shoemaker updated ZOOKEEPER-208: --- Attachment: zookeeper-strtok_getaddrinfo-trunk.patch Reattaching patch with licens

[jira] Commented: (ZOOKEEPER-208) Zookeeper C client uses API that are not thread safe, causing crashes when multiple instances are active

[ https://issues.apache.org/jira/browse/ZOOKEEPER-208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12648750#action_12648750 ] Patrick Hunt commented on ZOOKEEPER-208: Arg, jira won't allow me to wipe this.

[jira] Updated: (ZOOKEEPER-208) Zookeeper C client uses API that are not thread safe, causing crashes when multiple instances are active

[ https://issues.apache.org/jira/browse/ZOOKEEPER-208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-208: --- Comment: was deleted > Zookeeper C client uses API that are not thread safe, causing crash

[jira] Updated: (ZOOKEEPER-208) Zookeeper C client uses API that are not thread safe, causing crashes when multiple instances are active

[ https://issues.apache.org/jira/browse/ZOOKEEPER-208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-208: --- Description: The Zookeeper C client library uses gethostbyname and strtok, both of which a

[jira] Updated: (ZOOKEEPER-208) Zookeeper C client uses API that are not thread safe, causing crashes when multiple instances are active

[ https://issues.apache.org/jira/browse/ZOOKEEPER-208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Darroch updated ZOOKEEPER-208: Attachment: zookeeper-strtok_getaddrinfo-trunk.patch I've reformatted the original submi

[jira] Updated: (ZOOKEEPER-217) handle errors when parsing config file, throw illegalargumentexception rather than exit()

[ https://issues.apache.org/jira/browse/ZOOKEEPER-217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-217: --- Summary: handle errors when parsing config file, throw illegalargumentexception rather tha

ZooKeeper 3.0 Fix Release slated for end of this week.

I've slated the 3.0.1 fix release of ZooKeeper for the end of this week. https://issues.apache.org/jira/browse/ZOOKEEPER?report=com.atlassian.jira.plugin.system.project:roadmap-panel Of particular interest are exists() NPE in ZOOKEEPER-226, and some perf issues ZOOKEEPER-212 & ZOOKEEPER-223 If

[jira] Updated: (ZOOKEEPER-223) default log4j root logger configuration has neg perf impact with no benefit, change default level to INFO

[ https://issues.apache.org/jira/browse/ZOOKEEPER-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-223: --- Fix Version/s: 3.0.1 > default log4j root logger configuration has neg perf impact with no

Anyone expert in JMX willing to help with ZK impl/docs?

ZK 3.0.0 added support for JMX. Basic server stats are available, as are details on per-client connections. However we don't have zk specific documentation and also it would probably be a good idea for someone that's expert in JMX to review what we have and suggest changes. One thing that may f

[jira] Updated: (ZOOKEEPER-228) apache header missing in DBtest

[ https://issues.apache.org/jira/browse/ZOOKEEPER-228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahadev konar updated ZOOKEEPER-228: Resolution: Fixed Status: Resolved (was: Patch Available) Committed revision 71

[jira] Updated: (ZOOKEEPER-228) apache header missing in DBtest

[ https://issues.apache.org/jira/browse/ZOOKEEPER-228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahadev konar updated ZOOKEEPER-228: Hadoop Flags: [Reviewed] Status: Patch Available (was: Open) > apache header

[jira] Commented: (ZOOKEEPER-228) apache header missing in DBtest

[ https://issues.apache.org/jira/browse/ZOOKEEPER-228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12648733#action_12648733 ] Patrick Hunt commented on ZOOKEEPER-228: +1 looks good to me. > apache header

[jira] Updated: (ZOOKEEPER-228) apache header missing in DBtest

[ https://issues.apache.org/jira/browse/ZOOKEEPER-228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahadev konar updated ZOOKEEPER-228: Attachment: ZOOKEEPER-228.patch aatching the missing header. > apache header missing in

[jira] Updated: (ZOOKEEPER-227) gcc warning from recordio.h

[ https://issues.apache.org/jira/browse/ZOOKEEPER-227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-227: --- Fix Version/s: (was: 3.0.0) 3.1.0 Assignee: Chris Darroch

[jira] Created: (ZOOKEEPER-228) apache header missing in DBtest

apache header missing in DBtest --- Key: ZOOKEEPER-228 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-228 Project: Zookeeper Issue Type: Bug Affects Versions: 3.0.0 Reporter: Mahadev konar

[jira] Updated: (ZOOKEEPER-227) gcc warning from recordio.h

[ https://issues.apache.org/jira/browse/ZOOKEEPER-227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Darroch updated ZOOKEEPER-227: Status: Patch Available (was: Open) > gcc warning from recordio.h > ---

[jira] Updated: (ZOOKEEPER-227) gcc warning from recordio.h

[ https://issues.apache.org/jira/browse/ZOOKEEPER-227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Darroch updated ZOOKEEPER-227: Attachment: zookeeper-recordio-trunk.patch FWIW, I'm an Apache committer with a contribu

[jira] Updated: (ZOOKEEPER-227) gcc warning from recordio.h

[ https://issues.apache.org/jira/browse/ZOOKEEPER-227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Darroch updated ZOOKEEPER-227: Status: Patch Available (was: Open) > gcc warning from recordio.h > ---

[jira] Created: (ZOOKEEPER-227) gcc warning from recordio.h

gcc warning from recordio.h --- Key: ZOOKEEPER-227 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-227 Project: Zookeeper Issue Type: Bug Components: c client Affects Versions: 3.0.0 Rep

[jira] Commented: (ZOOKEEPER-226) exists calls fails on server if node has null data

[ https://issues.apache.org/jira/browse/ZOOKEEPER-226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12648725#action_12648725 ] Mahadev konar commented on ZOOKEEPER-226: - java.lang.NullPointerException

[jira] Updated: (ZOOKEEPER-227) gcc warning from recordio.h

[ https://issues.apache.org/jira/browse/ZOOKEEPER-227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Darroch updated ZOOKEEPER-227: Status: Open (was: Patch Available) > gcc warning from recordio.h > ---

[jira] Assigned: (ZOOKEEPER-226) exists calls fails on server if node has null data

[ https://issues.apache.org/jira/browse/ZOOKEEPER-226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahadev konar reassigned ZOOKEEPER-226: --- Assignee: Mahadev konar > exists calls fails on server if node has null data > ---

[jira] Created: (ZOOKEEPER-226) exists calls fails on server if node has null data

exists calls fails on server if node has null data -- Key: ZOOKEEPER-226 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-226 Project: Zookeeper Issue Type: Bug Components: server

[jira] Created: (ZOOKEEPER-225) c client should log an info message in zookeeper_init detailing connection parameters

c client should log an info message in zookeeper_init detailing connection parameters - Key: ZOOKEEPER-225 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-225 Pr

[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=12648686#action_12648686 ] Patrick Hunt commented on ZOOKEEPER-224: Hiram, couple things: 1) is the "GPG p

[jira] Resolved: (ZOOKEEPER-209) nullpointerexception if election port is not specified.

[ https://issues.apache.org/jira/browse/ZOOKEEPER-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahadev konar resolved ZOOKEEPER-209. - Resolution: Fixed fixed with ZOOKEEPER-217. > nullpointerexception if election port i

[jira] Updated: (ZOOKEEPER-217) Errors in config file

[ https://issues.apache.org/jira/browse/ZOOKEEPER-217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahadev konar updated ZOOKEEPER-217: Resolution: Fixed Hadoop Flags: [Reviewed] Status: Resolved (was: Patch

[jira] Commented: (ZOOKEEPER-217) Errors in config file

[ https://issues.apache.org/jira/browse/ZOOKEEPER-217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12648654#action_12648654 ] Flavio Paiva Junqueira commented on ZOOKEEPER-217: -- +1 looks good, maha

Build failed in Hudson: ZooKeeper-trunk #147

See http://hudson.zones.apache.org/hudson/job/ZooKeeper-trunk/147/changes Changes: [mahadev] ZOOKEEPER-219. fix events.poll timeout in watcher test to be longer. (pat via mahadev) [mahadev] ZOOKEEPER-213. fix programmer guide C api docs to be in sync with latest zookeeper.h (pat via mahadev)

[jira] Updated: (ZOOKEEPER-217) Errors in config file

[ https://issues.apache.org/jira/browse/ZOOKEEPER-217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahadev konar updated ZOOKEEPER-217: Status: Patch Available (was: Open) > Errors in config file > - > >

[jira] Updated: (ZOOKEEPER-217) Errors in config file

[ https://issues.apache.org/jira/browse/ZOOKEEPER-217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahadev konar updated ZOOKEEPER-217: Attachment: ZOOKEEPER-217.patch > we should use LOG.fatal instead of LOG.error when abou