Hi Ryan,
I have opened https://github.com/apache/curator/pull/464 in case you
are interested.
Best,
Kezhu Wang
On Mon, May 22, 2023 at 6:28 PM Ryan Ruel wrote:
>
> We’ve been using 5.5.0.
>
> That does look suspiciously close to what we are seeing!
>
> /Ryan
>
> > On May 22, 2023, at 2:54 AM,
We’ve been using 5.5.0.
That does look suspiciously close to what we are seeing!
/Ryan
> On May 22, 2023, at 2:54 AM, Kezhu Wang wrote:
>
> Hi Ryan,
>
> Which curator version did you use ? Is it possibly covered by
> CURATOR-673[1] (Complete BackgroundCallback if curator got closed or
> excep
Hi Ryan,
Which curator version did you use ? Is it possibly covered by
CURATOR-673[1] (Complete BackgroundCallback if curator got closed or
exceptions from no-zookeeper world) ?
[1]: https://issues.apache.org/jira/browse/CURATOR-673
Best,
Kezhu Wang
On Sat, May 20, 2023 at 12:44 PM tison wrot
Yep.
You're welcome to file a ticket on our JIRA project to share your
reproductive code - https://issues.apache.org/jira/projects/CURATOR
If you don't have a JIRA account yet, you can self-request at
https://selfserve.apache.org/jira-account.html
Best,
tison.
Ryan Ruel 于2023年5月19日周五 22:38写道：
It will require some effort to get there (without exposing proprietary code), but the goal would be reproduction (hopefully via unit test).Am I correct then in that these conditions are unexpected?Ryan Ruelr...@ryanruel.comOn May 19, 2023, at 9:33 AM, tison wrote:Hi Ryan,Thanks for reporting
Hi Ryan,
Thanks for reporting your use case!
According to your description, it's hard to investigate which part can be
the root cause of the hanging result. Could you provide a reproduce code
repo, or share the significant code snippet with related logs?
Best,
tison.
Ryan Ruel 于2023年5月19日周五 1
