Return-Path: X-Original-To: apmail-airavata-dev-archive@www.apache.org Delivered-To: apmail-airavata-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7D69717887 for ; Tue, 21 Apr 2015 17:34:42 +0000 (UTC) Received: (qmail 92096 invoked by uid 500); 21 Apr 2015 17:34:42 -0000 Delivered-To: apmail-airavata-dev-archive@airavata.apache.org Received: (qmail 92051 invoked by uid 500); 21 Apr 2015 17:34:42 -0000 Mailing-List: contact dev-help@airavata.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@airavata.apache.org Delivered-To: mailing list dev@airavata.apache.org Received: (qmail 92029 invoked by uid 99); 21 Apr 2015 17:34:42 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 Apr 2015 17:34:42 +0000 X-ASF-Spam-Status: No, hits=3.2 required=5.0 tests=HTML_MESSAGE,SPF_SOFTFAIL X-Spam-Check-By: apache.org Received-SPF: softfail (athena.apache.org: transitioning domain of glahiru@gmail.com does not designate 54.191.145.13 as permitted sender) Received: from [54.191.145.13] (HELO mx1-us-west.apache.org) (54.191.145.13) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 Apr 2015 17:34:36 +0000 Received: from mail-pa0-f54.google.com (mail-pa0-f54.google.com [209.85.220.54]) by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with ESMTPS id 58CB225793 for ; Tue, 21 Apr 2015 17:34:10 +0000 (UTC) Received: by pabtp1 with SMTP id tp1so247236200pab.2 for ; Tue, 21 Apr 2015 10:34:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=x5QM2MAlbSSIWkzdr58/OpT+uj/QqcYl0TiCUfTb6LU=; b=mt1Z+MPqLg2X2ncxl7uhXEI/2YAg9qV7d4c4mEBr02J8VT04dL98ySzrJkBN5dIBXj YjvdcY7P2k6dke7sx3DDm4os7W4JXkKrjezQLv19V5OamMJzK+f6vEwAip+O3P5PJ3DS yzB36gLjgpjQlvooFS027Q2MetKt2M7m4EYvB5iIp9o91ZMp39gFBL44qjPI+wEN5xhS VjHseNs8XcUxf72TvZz7bnGJOuS4xUhzV19TR+xoGCLnqIZBAk5+GeiJ/6pwLpbMCmUg NUSpkgOUgp4W+WPrimPey88DQWRmFdAYUuTucUY1drWhjsKWsl4N+96Zs059yuVWJ0bA E3bw== MIME-Version: 1.0 X-Received: by 10.70.89.102 with SMTP id bn6mr39865140pdb.48.1429637643957; Tue, 21 Apr 2015 10:34:03 -0700 (PDT) Received: by 10.66.86.2 with HTTP; Tue, 21 Apr 2015 10:34:03 -0700 (PDT) In-Reply-To: <5536893B.1070106@iu.edu> References: <5536893B.1070106@iu.edu> Date: Tue, 21 Apr 2015 13:34:03 -0400 Message-ID: Subject: Re: Replacing ZK client with Curator From: Lahiru Ginnaliya Gamathige To: dev Content-Type: multipart/alternative; boundary=001a11c22942ecfb3305143f733e X-Virus-Checked: Checked by ClamAV on apache.org --001a11c22942ecfb3305143f733e Content-Type: text/plain; charset=UTF-8 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 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 --001a11c22942ecfb3305143f733e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Its not=C2=A0= replace one set of problems with another, its about Curator is handling tim= eouts and other ZK client code we have to do, so we can directly use the Cu= rator code. Its like a helper library written using vanilla ZK client code.= =C2=A0

On Tue, Apr 21, 2015 at 1:30 PM, Marlon Pierce <marpierc@iu.edu> wrote:
Have you done a preliminary e= valuation?=C2=A0 We don't want to replace one set of problems with anot= her.

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<= br> 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=C2=A0Science Gateways Group
Indiana University
--001a11c22942ecfb3305143f733e--