Hi Lahiru, I only played with it very little, I was prototyping multiple API services and used curator service discovery recipe. I liked it from a development standpoint, do not have a opinion on how well it will help mitigate the issues you mention below. Hypothetically yes, but not sure in practice.
Should we just try it in a branch and validate it with the test framework? If it helps, I can bring this thread to attention of the curator pmc and seek expert advice, do we need it? Suresh > On Apr 21, 2015, at 1:34 PM, Lahiru Ginnaliya Gamathige <glah...@gmail.com> > 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 <marpi...@iu.edu > <mailto:marpi...@iu.edu>> 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
