Mailing-List: contact user-help@curator.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@curator.incubator.apache.org
Received-SPF: error (athena.apache.org: local policy)
From: Jordan Zimmerman <jordan@jordanzimmerman.com>
Content-Type: multipart/alternative;
 boundary="Apple-Mail=_E31E2850-A8DE-4328-9B04-89E45F1CA5AC"
Message-Id: <CF1E9065-976F-4EC4-92CB-347531A93584@jordanzimmerman.com>
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Status about two major bugs CURATOR-3 and CURATOR-45
Date: Thu, 1 Aug 2013 09:27:11 -0700
References: 
 <CAArVKB-8ypD4rsUPKPDorpxqJQ3h=X+1KUj+iKykkPczTOQ6yA@mail.gmail.com>
To: user@curator.incubator.apache.org
In-Reply-To: 
 <CAArVKB-8ypD4rsUPKPDorpxqJQ3h=X+1KUj+iKykkPczTOQ6yA@mail.gmail.com>


--Apple-Mail=_E31E2850-A8DE-4328-9B04-89E45F1CA5AC
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

I apologize these are taking so long. Curator recently got two =
additional committers (hopefully we can get more soon). So, response =
times should get better. I'll make a point of looking at these two for =
the next release.

-Jordan

On Aug 1, 2013, at 8:03 AM, chao chu <chuchao333@gmail.com> wrote:

> Hi,
>=20
> There are two 'major' bugs regarding leader election recipes:
>=20
> https://issues.apache.org/jira/browse/CURATOR-3
> https://issues.apache.org/jira/browse/CURATOR-45
>=20
> Do we have any plan to fix these?
>=20
> We are using the LeaderLatch, personally, I don't concern too much =
about CURATOR-3, I think that situation was caused partly by the client =
code, we can avoid this by coding carefully.
>=20
> However, when I introduced curator and the changes I made, some of my =
teammates become a little nervous when they saw there are 'major' bugs =
there.
>=20
> Is there any test case for re-producing the case mentioned there?
>=20
> Thanks,
>=20
>=20
> --=20
> ChuChao


--Apple-Mail=_E31E2850-A8DE-4328-9B04-89E45F1CA5AC
Content-Transfer-Encoding: 7bit
Content-Type: text/html;
	charset=iso-8859-1

<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>I apologize these are taking so long. Curator recently got two additional committers (hopefully we can get more soon). So, response times should get better. I'll make a point of looking at these two for the next release.</div><div><br></div><div>-Jordan</div><br><div><div>On Aug 1, 2013, at 8:03 AM, chao chu &lt;<a href="mailto:chuchao333@gmail.com">chuchao333@gmail.com</a>&gt; wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr">Hi,<div><br></div><div>There are two 'major' bugs regarding leader election recipes:</div><div><br></div><div><a href="https://issues.apache.org/jira/browse/CURATOR-3">https://issues.apache.org/jira/browse/CURATOR-3</a><br>

</div><div><a href="https://issues.apache.org/jira/browse/CURATOR-45">https://issues.apache.org/jira/browse/CURATOR-45</a></div><div><br></div><div>Do we have any plan to fix these?</div><div><br></div><div>We are using the LeaderLatch, personally, I don't concern too much about CURATOR-3, I think that situation was caused partly by the client code, we can avoid this by coding carefully.</div>

<div><br></div><div>However, when I introduced curator and the changes I made, some of my teammates become a little nervous when they saw there are 'major' bugs there.</div><div><br></div><div>Is there any test case for re-producing the case mentioned there?</div>

<div><br></div><div>Thanks,</div><div><br clear="all"><div><br></div>-- <br>ChuChao
</div></div>
</blockquote></div><br></body></html>
--Apple-Mail=_E31E2850-A8DE-4328-9B04-89E45F1CA5AC--