Re: About symbol table of Zookeeper c client

, perhaps this slipped through the net? Mahadev - can we address this using the current mechanism? https://issues.apache.org/jira/browse/ZOOKEEPER-295Patrick On Thu, Sep 2, 2010 at 7:37 AM, Qian Ye yeqian@gmail.com wrote: Hi all: I'm writing a application in C which need

About symbol table of Zookeeper c client

Hi all: I'm writing a application in C which need to link both memcached's lib and zookeeper's c client lib. I found a symbol table conflict, because both libs provide implmentation(recordio.h/c) of function htonll. It seems that some functions of zookeeper c client, which can be accessed

[jira] Commented: (ZOOKEEPER-797) c client source with AI_ADDRCONFIG cannot be compiled with early glibc

[ https://issues.apache.org/jira/browse/ZOOKEEPER-797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12883603#action_12883603 ] Qian Ye commented on ZOOKEEPER-797: --- Hi guys, do I need to add any tests

[jira] Updated: (ZOOKEEPER-797) c client source with AI_ADDRCONFIG cannot be compiled with early glibc

[ https://issues.apache.org/jira/browse/ZOOKEEPER-797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qian Ye updated ZOOKEEPER-797: -- Status: Patch Available (was: Open) c client source with AI_ADDRCONFIG cannot be compiled

[jira] Created: (ZOOKEEPER-797) c client source with AI_ADDRCONFIG cannot be compiled with early glibc

Issue Type: Improvement Components: c client Affects Versions: 3.3.1 Environment: linux 2.6.9 Reporter: Qian Ye Attachments: ZOOKEEPER-797.patch c client source with AI_ADDRCONFIG cannot be compiled with early glibc (before 2.3.3) -- This message

[jira] Updated: (ZOOKEEPER-797) c client source with AI_ADDRCONFIG cannot be compiled with early glibc

[ https://issues.apache.org/jira/browse/ZOOKEEPER-797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qian Ye updated ZOOKEEPER-797: -- Attachment: ZOOKEEPER-797.patch c client source with AI_ADDRCONFIG cannot be compiled with early

[jira] Commented: (ZOOKEEPER-779) C Client should check the connectivity to the hosts in zookeeper_init

[ https://issues.apache.org/jira/browse/ZOOKEEPER-779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12871474#action_12871474 ] Qian Ye commented on ZOOKEEPER-779: --- OK Patrick, however I'm really busy these days

[jira] Commented: (ZOOKEEPER-779) C Client should check the connectivity to the hosts in zookeeper_init

[ https://issues.apache.org/jira/browse/ZOOKEEPER-779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12870545#action_12870545 ] Qian Ye commented on ZOOKEEPER-779: --- By check connectivity, I mean check whether

[jira] Commented: (ZOOKEEPER-779) C Client should check the connectivity to the hosts in zookeeper_init

[ https://issues.apache.org/jira/browse/ZOOKEEPER-779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12870946#action_12870946 ] Qian Ye commented on ZOOKEEPER-779: --- Thx Patrick, i see your point. Here is some

[jira] Updated: (ZOOKEEPER-779) C Client should check the connectivity to the hosts in zookeeper_init

[ https://issues.apache.org/jira/browse/ZOOKEEPER-779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qian Ye updated ZOOKEEPER-779: -- Attachment: ZOOKEEPER-779.patch C Client should check the connectivity to the hosts

[jira] Updated: (ZOOKEEPER-779) C Client should check the connectivity to the hosts in zookeeper_init

[ https://issues.apache.org/jira/browse/ZOOKEEPER-779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qian Ye updated ZOOKEEPER-779: -- Status: Patch Available (was: Open) do the connectivity check in zookeeper_init C Client should

[jira] Updated: (ZOOKEEPER-779) C Client should check the connectivity to the hosts in zookeeper_init

[ https://issues.apache.org/jira/browse/ZOOKEEPER-779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qian Ye updated ZOOKEEPER-779: -- Attachment: ZOOKEEPER-779.patch C Client should check the connectivity to the hosts

[jira] Updated: (ZOOKEEPER-779) C Client should check the connectivity to the hosts in zookeeper_init

[ https://issues.apache.org/jira/browse/ZOOKEEPER-779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qian Ye updated ZOOKEEPER-779: -- Status: Patch Available (was: Open) C Client should check the connectivity to the hosts

[jira] Updated: (ZOOKEEPER-779) C Client should check the connectivity to the hosts in zookeeper_init

[ https://issues.apache.org/jira/browse/ZOOKEEPER-779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qian Ye updated ZOOKEEPER-779: -- Status: Open (was: Patch Available) C Client should check the connectivity to the hosts

[jira] Created: (ZOOKEEPER-779) C Client should check the connectivity to the hosts in zookeeper_init

Type: Improvement Components: c client Affects Versions: 3.3.1 Reporter: Qian Ye In some scenario, whether the client can connect to zookeeper servers is used as a logic condition. If the client cannot connect to the servers, the program should turn to another fork

[jira] Commented: (ZOOKEEPER-591) The C Client cannot exit properly in some situation

[ https://issues.apache.org/jira/browse/ZOOKEEPER-591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12844391#action_12844391 ] Qian Ye commented on ZOOKEEPER-591: --- This patch works for me, thx mahadev The C

[jira] Commented: (ZOOKEEPER-591) The C Client cannot exit properly in some situation

[ https://issues.apache.org/jira/browse/ZOOKEEPER-591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12843870#action_12843870 ] Qian Ye commented on ZOOKEEPER-591: --- The process still hang there, Mahadev. (gdb

Re: Google Summer of Code

Hi Henry, I think we should add two kinds of interface to the server: 1. An interface which can return the clients which set watcher on specific znode of the data tree. This kind of interface can be really helpful for the administrators. 2. An interface which can return a list of servers in a

[jira] Commented: (ZOOKEEPER-591) The C Client cannot exit properly in some situation

[ https://issues.apache.org/jira/browse/ZOOKEEPER-591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12843443#action_12843443 ] Qian Ye commented on ZOOKEEPER-591: --- Hi Mahadev, the patch doesn't work

Re: About load balance in Zookeeper server

/ZOOKEEPER-390 This might answer some of the problems you mention, but they are all being worked upon! Thanks mahadev On 3/1/10 6:09 PM, Qian Ye yeqian@gmail.com wrote: Thanks Mahadev, I see what you mean. Here is another question, the client need a list of Zookeeper servers

Re: About load balance in Zookeeper server

service because of some misbehaved client. Any other checks that you specifically were thinking of? Thanks mahadev On 2/28/10 10:18 PM, Qian Ye yeqian@gmail.com wrote: Hi guys: As I know, when a client connected to Zookeeper servers, it would choose a server randomly (without

About load balance in Zookeeper server

Hi guys: As I know, when a client connected to Zookeeper servers, it would choose a server randomly (without the zoo_deterministic_conn_odrder on), and then, the client would talk to the server until a failure happened. It seems that zookeeper server cannot handle the client connection

[jira] Commented: (ZOOKEEPER-662) Too many CLOSE_WAIT socket state on a server

[ https://issues.apache.org/jira/browse/ZOOKEEPER-662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12837696#action_12837696 ] Qian Ye commented on ZOOKEEPER-662: --- This has not happened again yet

[jira] Commented: (ZOOKEEPER-662) Too many CLOSE_WAIT socket state on a server

[ https://issues.apache.org/jira/browse/ZOOKEEPER-662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12838157#action_12838157 ] Qian Ye commented on ZOOKEEPER-662: --- Thx Patrick, this situation might be consequence

[jira] Commented: (ZOOKEEPER-662) Too many CLOSE_WAIT socket state on a server

[ https://issues.apache.org/jira/browse/ZOOKEEPER-662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12829920#action_12829920 ] Qian Ye commented on ZOOKEEPER-662: --- Hi Patrick, the c clients all run in a Linux

[jira] Commented: (ZOOKEEPER-662) Too many CLOSE_WAIT socket state on a server

[ https://issues.apache.org/jira/browse/ZOOKEEPER-662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12828916#action_12828916 ] Qian Ye commented on ZOOKEEPER-662: --- I'm using the c client, and there is also

[jira] Created: (ZOOKEEPER-662) Too many CLOSE_WAIT socket state on a server

Affects Versions: 3.2.1 Environment: Linux 2.6.9 Reporter: Qian Ye Fix For: 3.3.0 I have a zookeeper cluster with 5 servers, zookeeper version 3.2.1, here is the content in the configure file, zoo.cfg == # The number of milliseconds of each tick tickTime=2000

[jira] Updated: (ZOOKEEPER-662) Too many CLOSE_WAIT socket state on a server

[ https://issues.apache.org/jira/browse/ZOOKEEPER-662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qian Ye updated ZOOKEEPER-662: -- Attachment: zookeeper.log.2010020106 zookeeper.log.2010020105 related log

[jira] Updated: (ZOOKEEPER-612) Make Zookeeper C client can be compiled by gcc of early version

[ https://issues.apache.org/jira/browse/ZOOKEEPER-612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qian Ye updated ZOOKEEPER-612: -- Release Note: (was: fix a semicolon mistake) Status: Patch Available (was: Open) Make

[jira] Updated: (ZOOKEEPER-612) Make Zookeeper C client can be compiled by gcc of early version

[ https://issues.apache.org/jira/browse/ZOOKEEPER-612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qian Ye updated ZOOKEEPER-612: -- Status: Open (was: Patch Available) update the patch Make Zookeeper C client can be compiled

[jira] Updated: (ZOOKEEPER-612) Make Zookeeper C client can be compiled by gcc of early version

[ https://issues.apache.org/jira/browse/ZOOKEEPER-612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qian Ye updated ZOOKEEPER-612: -- Attachment: ZOOKEEPER-612.patch Make Zookeeper C client can be compiled by gcc of early version

[jira] Updated: (ZOOKEEPER-612) Make Zookeeper C client can be compiled by gcc of early version

[ https://issues.apache.org/jira/browse/ZOOKEEPER-612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qian Ye updated ZOOKEEPER-612: -- Release Note: update the path, hope it works this time Status: Patch Available (was: Open

[jira] Commented: (ZOOKEEPER-650) Servers cannot join in quorum

[ https://issues.apache.org/jira/browse/ZOOKEEPER-650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12802819#action_12802819 ] Qian Ye commented on ZOOKEEPER-650: --- Hi all, some more information about this problem

[jira] Updated: (ZOOKEEPER-612) Make Zookeeper C client can be compiled by gcc of early version

[ https://issues.apache.org/jira/browse/ZOOKEEPER-612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qian Ye updated ZOOKEEPER-612: -- Attachment: ZOOKEEPER-612.patch New patch against trunk Make Zookeeper C client can be compiled

[jira] Commented: (ZOOKEEPER-612) Make Zookeeper C client can be compiled by gcc of early version

[ https://issues.apache.org/jira/browse/ZOOKEEPER-612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12801347#action_12801347 ] Qian Ye commented on ZOOKEEPER-612: --- Is that because I didn't make the patch based

[jira] Commented: (ZOOKEEPER-628) the ephemeral node wouldn't disapper due to session close error

[ https://issues.apache.org/jira/browse/ZOOKEEPER-628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12797870#action_12797870 ] Qian Ye commented on ZOOKEEPER-628: --- err...sorry, i wasn't aware of these comments

[jira] Updated: (ZOOKEEPER-612) Make Zookeeper C client can be compiled by gcc of early version

[ https://issues.apache.org/jira/browse/ZOOKEEPER-612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qian Ye updated ZOOKEEPER-612: -- Attachment: ZOOKEEPER-612.patch yes Patrick, reasonable tips, a patch for this is attached, thx

[jira] Updated: (ZOOKEEPER-612) Make Zookeeper C client can be compiled by gcc of early version

[ https://issues.apache.org/jira/browse/ZOOKEEPER-612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qian Ye updated ZOOKEEPER-612: -- Release Note: fix a semicolon mistake Status: Patch Available (was: Open) Make

[jira] Updated: (ZOOKEEPER-612) Make Zookeeper C client can be compiled by gcc of early version

[ https://issues.apache.org/jira/browse/ZOOKEEPER-612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qian Ye updated ZOOKEEPER-612: -- Status: Open (was: Patch Available) Make Zookeeper C client can be compiled by gcc of early

[jira] Updated: (ZOOKEEPER-612) Make Zookeeper C client can be compiled by gcc of early version

[ https://issues.apache.org/jira/browse/ZOOKEEPER-612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qian Ye updated ZOOKEEPER-612: -- Attachment: patch fix a semicolon mistake Make Zookeeper C client can be compiled by gcc of early

A very strange scenario, may due to some bug on the server side

Hi guys: I find a very strange scenario today, I'm not sure how it happen, I just found it like this. Maybe you can give me some information about it, my Zookeeper Server is version 3.2.1. My Zookeeper cluster contains three servers, with ip: 10.81.12.144,10.81.12.145,10.81.12.141. I wrote a

[jira] Commented: (ZOOKEEPER-628) the ephemeral node wouldn't disapper due to session close error

[ https://issues.apache.org/jira/browse/ZOOKEEPER-628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12791121#action_12791121 ] Qian Ye commented on ZOOKEEPER-628: --- P.S. se/diserver_tc/diserver_tc67 is only

Re: A very strange scenario, may due to some bug on the server side

, Patrick Hunt ph...@apache.org wrote: You might also try the dump command for all 3 servers (similar to the stat command - it's a 4letterword) and look at it's output -- it includes information on ephemeral nodes. Patrick Qian Ye wrote: Hi guys: I find a very strange scenario today, I'm

[jira] Commented: (ZOOKEEPER-628) the ephemeral node wouldn't disapper due to session close error

[ https://issues.apache.org/jira/browse/ZOOKEEPER-628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12791134#action_12791134 ] Qian Ye commented on ZOOKEEPER-628: --- the 'dump' information for the three servers

Re: A very strange scenario, may due to some bug on the server side

se/diserver_tc/diserver_tc67 appear on all three servers? ben Qian Ye wrote: Hi guys: I find a very strange scenario today, I'm not sure how it happen, I just found it like this. Maybe you can give me some information about it, my Zookeeper Server is version 3.2.1. My

The C Client cause core dump in some situation

Hi guys: I encountered a problem today that the Zookeeper C Client (version 3.2.0) core dump when reconnected and did some operations on the zookeeper server which just restarted. The gdb infomation is like: (gdb) bt #0 0x00302af71900 in memcpy () from /lib64/tls/libc.so.6 #1

[jira] Created: (ZOOKEEPER-624) The C Client cause core dump when receive error data from Zookeeper Server

Issue Type: Bug Components: c client Affects Versions: 3.2.0 Environment: Linux 2.6.9 x86_64 Reporter: Qian Ye I encountered a problem today that the Zookeeper C Client (version 3.2.0) core dump when reconnected and did some operations on the zookeeper

Re: The C Client cause core dump in some situation

have any test case or a test scenario where it can be reproduced. It would be interesting to see why this is happening. We should not be getting a -1 len value from the server. Thanks mahadev On 12/14/09 6:19 AM, Qian Ye yeqian@gmail.com wrote: Hi guys: I encountered a problem

Re: The C Client cause core dump in some situation

Yes, I use valgrind, i will try. On Tue, Dec 15, 2009 at 1:02 PM, Patrick Hunt ph...@apache.org wrote: Did you try using valgrind? That might help reproduce. Qian Ye wrote: Hi Mahadev: I have created a jira for this issue https://issues.apache.org/jira/browse/ZOOKEEPER-624. And so far

[jira] Created: (ZOOKEEPER-612) Make Zookeeper C client can be compiled by gcc of early version

: Improvement Components: c client Affects Versions: 3.2.1 Environment: Linux Reporter: Qian Ye The original C Client, Version 3.2.1, cannot be compiled successfully by the gcc of early version, due some declaration restriction. To compile the source code

[jira] Updated: (ZOOKEEPER-612) Make Zookeeper C client can be compiled by gcc of early version

[ https://issues.apache.org/jira/browse/ZOOKEEPER-612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Qian Ye updated ZOOKEEPER-612: -- Attachment: patch can be compiled by gcc 2.96 Make Zookeeper C client can be compiled by gcc

[jira] Created: (ZOOKEEPER-591) The C Client cannot exit properly in some situation

client Affects Versions: 3.2.1 Environment: Linux db-passport-test05.vm 2.6.9_5-4-0-5 #1 SMP Tue Apr 14 15:56:24 CST 2009 x86_64 x86_64 x86_64 GNU/Linux Reporter: Qian Ye The following code produce a situation, where the C Client can not exit properly, #include include

[jira] Created: (ZOOKEEPER-589) When create a znode, a NULL ACL parameter cannot be accepted

Components: c client Affects Versions: 3.2.1 Environment: Linux db-passport-test05.vm 2.6.9_5-4-0-5 #1 SMP Tue Apr 14 15:56:24 CST 2009 x86_64 x86_64 x86_64 GNU/Linux Reporter: Qian Ye In the comments of client C API which associated with creating znode, eg

How to build Zookeeper Server in Eclipse?

Hi all: Recently, I built a system for resource discovery based on Zookeeper. It works well, which makes me want to study the internals of Zookeeper Server. However, I'm a greenhorn to Java. After loading the source into eclipse and reading the code for several days, I still don't no how to build

[jira] Created: (ZOOKEEPER-515) Zookeeper quorum didn't provide service when restart after an Out of memory crash

: Zookeeper Issue Type: Bug Components: server Affects Versions: 3.2.0 Environment: Linux 2.6.9-52bs-4core #2 SMP Wed Jan 16 14:44:08 EST 2008 x86_64 x86_64 x86_64 GNU/Linux Jdk: 1.6.0_14 Reporter: Qian Ye The Zookeeper quorum, containing 5 servers