jira-importer

Results 1253 comments of jira-importer

[CURATOR-467] Avoid logging errors after curator framework is closed.

[Originally related to: CURATOR-469]

[CURATOR-318] Threads may return different boolean values when entering same double barrier

shiliang: Attachment is my codes to reproduce this issue.

[CURATOR-318] Threads may return different boolean values when entering same double barrier

randgalt: I ran the test but I have no idea what I'm looking at. Please re-write the test as a TestNG unit test with an asserts, etc. that show the...

[CURATOR-318] Threads may return different boolean values when entering same double barrier

randgalt: Also, a Pull Request with a fix would be appreciated.

[CURATOR-318] Threads may return different boolean values when entering same double barrier

htuy: I added a test for the problem. I've done a PR of a simple fix, which mostly resolved the problem. I believe there are still potential race conditions, but...

[CURATOR-510] A serious death cycle error. 使用TreeCache时，当path的不存在时，出现死循环调用zookeeper server。

randgalt: No one on the team speaks Chinese. Please rewrite this ticket in English

[CURATOR-469] Give background task a chance to execute in CuratorFramework.close()

cammckenzie: This sounds like a sensible approach, and I think it will fix a number of issues: CURATOR-448, CURATOR-467 and CURATOR-468 Would you like to submit a PR for this...

[CURATOR-355] Curator client fails when connecting to read-only ensemble

randgalt: Is this Curator 3.x? or 2.x?

[CURATOR-355] Curator client fails when connecting to read-only ensemble

benjamin.jaton: I used Curator 2.11.0.

[CURATOR-355] Curator client fails when connecting to read-only ensemble

randgalt: Firstly, the call to client.getZookeeperClient().blockUntilConnectedOrTimedOut(); is unnecessary as Curator does this internally. Curator 3.0 has better connection timeout behavior than Curator 2.0. In 2.0, the connection timeout is applied...