+1 for replacing with apache curator. I updated dev server after
yesterday's updates. Eroma ran her test scripts and yesterday and I can see
some jobs are running today as well. I don't see any blockers related to ZK
timeout and connection losses.

On Tue, Apr 21, 2015 at 1:34 PM, Lahiru Ginnaliya Gamathige <
[email protected]> wrote:

> Its not replace one set of problems with another, its about Curator is
> handling timeouts and other ZK client code we have to do, so we can
> directly use the Curator code. Its like a helper library written using
> vanilla ZK client code.
>
> On Tue, Apr 21, 2015 at 1:30 PM, Marlon Pierce <[email protected]> wrote:
>
>> Have you done a preliminary evaluation?  We don't want to replace one set
>> of problems with another.
>>
>> Marlon
>>
>>
>> On 4/21/15 12:39 PM, Lahiru Ginnaliya Gamathige wrote:
>>
>>> Hi Devs,
>>>
>>> I think its a good idea to replace ZK client code with Apache Curator
>>> because we have to handle lots of timeout and other connectionLost issues
>>> manually.
>>>
>>> What do you think, is it too late to do this and do the release ? If so
>>> we
>>> can do it in next release otherwise we can implement this and extend the
>>> release bit further.
>>>
>>> Are there any blocker like issues cause due to ZK timeout and
>>> connectionLost errors ?
>>>
>>> Regards
>>> Lahiru
>>>
>>>
>>
>
>
> --
> Research Assistant
> Science Gateways Group
> Indiana University
>

Reply via email to