Hi Shameera, I am not opposed to moving to curator, it indeed might help since as Jordan described on a different thread, curator will monitor connections and retry them without airavata not having to do the similar handling of connection failures. But my understanding is they are for more transient.
I am curious what kind of connection issues have you seen lately (when we are directly using zookeeper client)? Suresh > On May 28, 2015, at 11:58 AM, Shameera Rathnayaka <[email protected]> wrote: > > Hi Devs, > > Following actions have been taken with Apache Curator Integration. > > 1. Remove Zookeeper dependency from Orchestrator module[1]. > 2. Use one CuratorFramework object everywhere in Gfac[2]. > 3. Removed unused utils methods related to Zookeeper. > 4. Use latest Curator release (2.8.0) > > TODO, > need to review zookeeper data structure. > > [1] > https://github.com/apache/airavata/commit/915ed04d54c61e083ef0f2b7dccb7083ef3fee9e > > <https://github.com/apache/airavata/commit/915ed04d54c61e083ef0f2b7dccb7083ef3fee9e> > [2] > https://github.com/apache/airavata/commit/4a06178022c0cd1a215c47e3c65a7b6ffd342bbb > > <https://github.com/apache/airavata/commit/4a06178022c0cd1a215c47e3c65a7b6ffd342bbb> > > Thanks, > Shameera.
