Thanks Ted, The link was indeed helpful. The issue is that whenever we hit this exception, since the HBASE writes are individual tasks in a threadpool, this exception causes the application to go in crazy loop and the handle never comes to the parent thread.
Sesondly, is it a good idea if I write a custom pool which manages the htable life cycle using the commons pool framework instead of relying on the htablepool or the Hconnection?? -- View this message in context: http://apache-hbase.679495.n3.nabble.com/Zookeeper-timeout-exception-seen-whenever-too-much-of-data-is-being-pushed-to-hbase-tp4060560p4060566.html Sent from the HBase User mailing list archive at Nabble.com.
