Hello, I am the maintainer of Stargate.
The next time you see this problem, please provide the Stargate client log for examination. > - SG base64 encodes all the output which is good, but it'd be great if it was > made a painfully plain stating the obvious fact on the wiki for boneheads > like > myself Ok. Will do more doc for next release. > - I saw that SG is probably going to have some authentication features and > caching added, will it also be possible to explicitly disable them, because I > would rather use a dedicated reverse proxy for that I agree with this -- it's the appropriate way to stack that feature in a RESTful architecture -- so I wouldn't worry too much about caching in Stargate. If there is some caching added due to good reason for some use case, it will for sure be turned off by default. Regarding authentication, this is dependent on how the authentication portion of HBASE-1697 works out. Such an authentication feature would only be active if it is running in daemon mode. When deployed as a servlet, Stargate will rely instead on whatever authentication/authorization mechanisms are supported by the servlet container and configured by the administrator. - Andy ----- Original Message ---- > From: "Gibbon, Robert, VF-Group" <[email protected]> > To: [email protected] > Sent: Wed, December 23, 2009 6:00:49 AM > Subject: Zookeeper session prb > > Hello, > > I am playing around with Hbase and the Stargate interface; I got a problem > when > I came back from lunch which rendered my little test rig unavailable and I > had > to restart it. > > I'm running a pseudo cluster on an ubuntu vm, 0.20.2 of Hbase and all the > defaults. I haven't changed anything in limits.conf on the vm but I think > this > is a lunch/time triggered issue? Has anybody seen this one before if so > what's > the workaround? It looks a bit like it could connection/file descriptor leak > too > from my limited experience in these things. See the dump of log below. > > I have two other minor comments on the excellent SG interface > > - SG base64 encodes all the output which is good, but it'd be great if it was > made a painfully plain stating the obvious fact on the wiki for boneheads > like > myself > - I saw that SG is probably going to have some authentication features and > caching added, will it also be possible to explicitly disable them, because I > would rather use a dedicated reverse proxy for that > > 09/12/23 13:41:05 WARN zookeeper.ClientCnxn: Exception closing session > 0x125bafce85d0006 to sun.nio.ch.selectionkeyi...@16d46d7 > java.io.IOException: TIMED OUT > at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:906) > 09/12/23 13:41:43 DEBUG client.HConnectionManager$ClientZKWatcher: Got > ZooKeeper > event, state: Disconnected, type: None, path: null > 09/12/23 13:42:50 WARN zookeeper.ClientCnxn: Exception closing session > 0x125bafce85d0006 to sun.nio.ch.selectionkeyi...@227d4e > java.io.IOException: TIMED OUT > at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:906) > 09/12/23 13:43:47 WARN zookeeper.ClientCnxn: Exception closing session > 0x125bafce85d0006 to sun.nio.ch.selectionkeyi...@8d8f67 > java.io.IOException: TIMED OUT > at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:906) > 09/12/23 13:44:39 WARN zookeeper.ClientCnxn: Exception closing session > 0x125bafce85d0006 to sun.nio.ch.selectionkeyi...@1c1eceb > java.io.IOException: TIMED OUT > at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:906) > 09/12/23 13:44:51 WARN zookeeper.ClientCnxn: Exception closing session > 0x125bafce85d0006 to sun.nio.ch.selectionkeyi...@a96863 > java.io.IOException: Session Expired > at > org.apache.zookeeper.ClientCnxn$SendThread.readConnectResult(ClientCnxn.java:589) > at org.apache.zookeeper.ClientCnxn$SendThread.doIO(ClientCnxn.java:709) > at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:945) > 09/12/23 13:44:51 DEBUG client.HConnectionManager$ClientZKWatcher: Got > ZooKeeper > event, state: Expired, type: None, path: null > 09/12/23 13:44:56 DEBUG zookeeper.ZooKeeperWrapper: Closed connection with > ZooKeeper > > > Robert Gibbon > Solutions Architect > Integration Design & Solution Engineering > > [email protected] > +32 474 53 52 51 > > Vodafone Group Service GmbH > Mannesmannufer 2, D-40213 Düsseldorf, Germany > Amtsgericht Düsseldorf, HRB 53554 > Geschäftsführung: Helmut Hoffmann, Dr. Joachim Peters
