RE: Storing znode on disks

2013-03-14 Thread Rakesh R
Hi Abishek, Could you give more on the data set and the use case in detail. ZooKeeper is desgined to manage co-ordination data and not designed to be a general database or large object store. Usually the co-ordination data will be relatively small: measured in kilobytes. If the data size is ver

[jira] [Updated] (ZOOKEEPER-1667) Watch event isn't handled correctly when a client reestablish to a server

2013-03-14 Thread Jacky007 (JIRA)
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacky007 updated ZOOKEEPER-1667: Description: When a client reestablish to a server, it will send the watches which have not be

[jira] [Updated] (ZOOKEEPER-1667) Watch event isn't handled correctly when a client reestablish to a server

2013-03-14 Thread Jacky007 (JIRA)
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacky007 updated ZOOKEEPER-1667: Description: When a client reestablish to a server, it will send the watches which have not be

[jira] [Updated] (ZOOKEEPER-1667) Watch event isn't handled correctly when a client reestablish to a server

2013-03-14 Thread Jacky007 (JIRA)
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacky007 updated ZOOKEEPER-1667: Description: When a client reestablish to a server, it will send the watches which have not be

[jira] [Updated] (ZOOKEEPER-1666) Avoid Reverse DNS lookup if the hostname in connection string is literal IP address.

2013-03-14 Thread George Cao (JIRA)
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] George Cao updated ZOOKEEPER-1666: -- Hadoop Flags: Reviewed (was: Incompatible change,Reviewed) > Avoid Reverse DNS lookup

Re: Storing znode on disks

2013-03-14 Thread Thawan Kooburat
This depends on the data size and availability requirement of your use case. Ideally, the size of RAM limit the total data size for ZooKeeper. However, if you store several gigs of data into ZooKeeper, the server load time will be quite long (minutes) depending on your disk bandwidth. When there i

Re: Storing znode on disks

2013-03-14 Thread Abhishek .E.S
Could I build a large scale data-store using Zookeeper though ? On Thu, Mar 14, 2013 at 12:52 PM, Edward Ribeiro wrote: > >> For me, latency is acceptable but I require the znodes to be on disk. > > Why would you need to do that? > > ZooKeeper stores the dataTree in memory, but it performs perio

Re: Storing znode on disks

2013-03-14 Thread Edward Ribeiro
>> For me, latency is acceptable but I require the znodes to be on disk. Why would you need to do that? ZooKeeper stores the dataTree in memory, but it performs periodic snapshots to disk, besides sync-ing a commit log also to disk, so that a node can recover in case of failures. If you are aski

[jira] [Commented] (ZOOKEEPER-1666) Avoid Reverse DNS lookup if the hostname in connection string is literal IP address.

2013-03-14 Thread George Cao (JIRA)
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13602412#comment-13602412 ] George Cao commented on ZOOKEEPER-1666: --- The key is we need to set the *hostName

[jira] [Commented] (ZOOKEEPER-1666) Avoid Reverse DNS lookup if the hostname in connection string is literal IP address.

2013-03-14 Thread George Cao (JIRA)
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13602372#comment-13602372 ] George Cao commented on ZOOKEEPER-1666: --- [~sbridges], I am pretty sure that ZOOK

[jira] [Updated] (ZOOKEEPER-1667) Watch event isn't handled correctly when a client reestablish to a server

2013-03-14 Thread Jacky007 (JIRA)
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacky007 updated ZOOKEEPER-1667: Summary: Watch event isn't handled correctly when a client reestablish to a server (was: Watch

[jira] [Updated] (ZOOKEEPER-1667) Watch event is handled incorrectly when a client reestablish to a server

2013-03-14 Thread Jacky007 (JIRA)
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacky007 updated ZOOKEEPER-1667: Summary: Watch event is handled incorrectly when a client reestablish to a server (was: Watch

[jira] [Commented] (ZOOKEEPER-1379) 'printwatches, redo, history and connect '. client commands always print usage. This is not necessary

2013-03-14 Thread Edward Ribeiro (JIRA)
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13602263#comment-13602263 ] Edward Ribeiro commented on ZOOKEEPER-1379: --- Hi folks, any interest on commi

[jira] [Commented] (ZOOKEEPER-1666) Avoid Reverse DNS lookup if the hostname in connection string is literal IP address.

2013-03-14 Thread Sean Bridges (JIRA)
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13602262#comment-13602262 ] Sean Bridges commented on ZOOKEEPER-1666: - Does the patch to ZOOKEEPER-1652 fi

[jira] [Commented] (ZOOKEEPER-1531) Correct the documentation of the args for the JavaExample doc.

2013-03-14 Thread Edward Ribeiro (JIRA)
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13602259#comment-13602259 ] Edward Ribeiro commented on ZOOKEEPER-1531: --- This issue should be closed bec

ZooKeeper-trunk-solaris - Build # 497 - Still Failing

2013-03-14 Thread Apache Jenkins Server
See https://builds.apache.org/job/ZooKeeper-trunk-solaris/497/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 208397 lines...] [junit] 2013-03-14 12:12:51,963

ZooKeeper-trunk - Build # 1864 - Still Failing

2013-03-14 Thread Apache Jenkins Server
See https://builds.apache.org/job/ZooKeeper-trunk/1864/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 298790 lines...] [junit] 2013-03-14 11:01:59,898 [myid:

[jira] [Updated] (ZOOKEEPER-1667) Watch event is handled incorrect when a client reestablish to a server

2013-03-14 Thread Jacky007 (JIRA)
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacky007 updated ZOOKEEPER-1667: Attachment: ZOOKEEPER-1667.patch > Watch event is handled incorrect when a client reestabli

[jira] [Updated] (ZOOKEEPER-1667) Watch event is handled incorrect when a client reestablish to a server

2013-03-14 Thread Jacky007 (JIRA)
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacky007 updated ZOOKEEPER-1667: Description: When a client reestablish to a server, it will send the watches which have not be

[jira] [Created] (ZOOKEEPER-1667) Watch event is handled incorrect when a client reestablish to a server

2013-03-14 Thread Jacky007 (JIRA)
Jacky007 created ZOOKEEPER-1667: --- Summary: Watch event is handled incorrect when a client reestablish to a server Key: ZOOKEEPER-1667 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1667 Project: Z

ZooKeeper_branch33_solaris - Build # 470 - Failure

2013-03-14 Thread Apache Jenkins Server
See https://builds.apache.org/job/ZooKeeper_branch33_solaris/470/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 100106 lines...] [junit] 2013-03-14 07:02:50,