You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by GitBox <gi...@apache.org> on 2019/11/08 22:35:48 UTC

[GitHub] [accumulo] keith-turner commented on issue #1086: ZooLock uses ZooReader which may retry on session expired

keith-turner commented on issue #1086: ZooLock uses ZooReader which may retry on session expired
URL: https://github.com/apache/accumulo/issues/1086#issuecomment-552017270
 
 
   I looked into this a bit today.  Another issue I discovered with ZooLock's use of ZooReader is that it automatically creates new Zookeeper objects when a session has expired.  I am not sure if this is causing any problems, but its a concern I have.  The following is some background info.
   
    * Zookeeper objects have a one to relationship with a zookeeper session.  When a session expires zookeeper objects become non-functional.
    * Zoolock relies on ephemeral nodes which are automatically deleted when a session expires.
   
   It may be ok that new Zookeeper objects are automatically created because the ephemeral node will cease to exist and this would be visible through the new zookeeper object.
   
   Because of the tight coupling between zoolock, ephemeral nodes, zookeeper objects, and zookeeper sessions I think it may be better if zoolock directly uses zookeeper w/o any intermediate abstraction layer.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services