Mahadev, There are couple of reasons: a) We want to use our Web GUI to create/update/delete the data. (which is basically our own internal configuration information) This helps our operation team don't have to use any external tool for handling ZK data. b)We have to run separate file servers for this particular usage. If it's in database, it's easy to extend our web gui and then use the existing mechanism for the data backup.
Best, -Uday. ________________________________ From: Mahadev Konar <[email protected]> To: [email protected]; Uday Subbarayan <[email protected]> Sent: Wednesday, September 7, 2011 11:47 AM Subject: Re: zookeeper connection loss exception occurs on new created ZooKeeper instance too much,why? Uday, I dont see why you'd want to do that? For security you could run ZK as a user only which can access the data/snapshot dir for the ZK servers. I am not sure how putting it in database would make it more secure? thanks mahadev On Wed, Sep 7, 2011 at 11:17 AM, Uday Subbarayan <[email protected]> wrote: > Mahadev, > I mean the data that we store in ZK is currently persisted in a > file system. The config file has the location and ZK stores the data in that > location. For security reasons, we are wondering whether we can store our > data in a database? > > *We are fine to have the current mechanism of config file in a file system. > > Thanks, > -Uday. > > ------------------------- > I do not blog but e-write: > http://uds-web.blogspot.com > > > ________________________________ > From: Mahadev Konar <[email protected]> > To: [email protected] > Sent: Wednesday, September 7, 2011 12:58 AM > Subject: Re: zookeeper connection loss exception occurs on new created > ZooKeeper instance too much,why? > > Isaac, > You should wait for the state to be connected before issuing the requests. > > Take a look at the javadoc: > > http://bit.ly/oC6TEb > > hope that helps > mahadev > > > On Wed, Sep 7, 2011 at 12:48 AM, Isaac <[email protected]> wrote: >> oh, i found this, operate on a zookeeper in status CONNECTING will throw a >> ConnectionLossException. >> maybe that's the problem. >> example: >> [zk: 172.27.1.1:8082(CONNECTING) 1] ls / >> Exception in thread "main" org.apache.zookeeper.KeeperException$ >> ConnectionLossException: KeeperErrorCode = ConnectionLoss for / >> at >> org.apache.zookeeper.KeeperException.create(KeeperException.java:90) >> at >> org.apache.zookeeper.KeeperException.create(KeeperException.java:42) >> at org.apache.zookeeper.ZooKeeper.getChildren(ZooKeeper.java:1243) >> at org.apache.zookeeper.ZooKeeper.getChildren(ZooKeeper.java:1271) >> at >> org.apache.zookeeper.ZooKeeperMain.processZKCmd(ZooKeeperMain.java:700) >> at >> org.apache.zookeeper.ZooKeeperMain.processCmd(ZooKeeperMain.java:581) >> at >> org.apache.zookeeper.ZooKeeperMain.executeLine(ZooKeeperMain.java:353) >> at org.apache.zookeeper.ZooKeeperMain.run(ZooKeeperMain.java:311) >> at org.apache.zookeeper.ZooKeeperMain.main(ZooKeeperMain.java:270) >> >> On Wed, Sep 7, 2011 at 3:32 PM, Isaac <[email protected]> wrote: >> >>> zookeeper connection loss exception occurs on new created ZooKeeper >>> instance too much >>> >>> code like this: >>> ZooKeeper zk = new ZooKeeper(connectString, 3000, defaultWatcher); >>> zk.exists("/"); //connection loss exception occurs here sometimes. >>> >>> any one knows why? >>> >>> >>> >>
