Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Zk-based AsyncMap get() call fails silently #129

Open
yifangl opened this issue Aug 15, 2022 · 0 comments
Open

Zk-based AsyncMap get() call fails silently #129

yifangl opened this issue Aug 15, 2022 · 0 comments
Milestone

Comments

@yifangl
Copy link

yifangl commented Aug 15, 2022

Questions

The get() method of the AsyncMap used in our app sometimes just times out without going into the callback handler. As a result we are not able to handle it in the callback handler. It looks like a silent failure and the get() call just hangs until the vertx times out.

Version

Current version under use is 3.9.13

Context

Our code is using the Zk-based AsyncMap as follow:

asyncMap.get(currentNodeId, new Handler<AsyncResult>() {
@OverRide
public void handle(AsyncResult findNodeInfoResult) {
if (findNodeInfoResult.failed()) {
LOG.error("Failed to find nodeInfo by live node id {}", currentNodeId, findNodeInfoResult.cause());
} else {
LOG.debug("Fetched nodeInfo {} for {}.", findNodeInfoResult.result(), currentNodeId);
}
});

And through the log we can see sometimes the get() just fail silently and times out, neither the LOG.error(), nor the LOG.debug() can be seen in the server log. We were expecting in case of this, it should at least go to the failed() case and so we expect to see logs like LOG.error("Failed to find nodeInfo by live node id {}", currentNodeId, findNodeInfoResult.cause());

Wondering if this a known issue? Could you help to review and suggest best way to solve this?

@vietj vietj added this to the 4.3.4 milestone Aug 16, 2022
@vietj vietj modified the milestones: 4.3.4, 4.3.5 Oct 1, 2022
@vietj vietj modified the milestones: 4.3.5, 4.4.0 Nov 18, 2022
@vietj vietj modified the milestones: 4.4.0, 4.4.1 Mar 2, 2023
@vietj vietj modified the milestones: 4.4.1, 4.4.2 Mar 31, 2023
@vietj vietj modified the milestones: 4.4.2, 4.4.3 May 12, 2023
@vietj vietj modified the milestones: 4.4.3, 4.4.4-SNAPSHOT, 4.4.4 Jun 7, 2023
@vietj vietj modified the milestones: 4.4.4, 4.4.5 Jun 22, 2023
@vietj vietj modified the milestones: 4.4.5, 4.4.6 Aug 30, 2023
@vietj vietj modified the milestones: 4.4.6, 4.5.0 Sep 12, 2023
@vietj vietj modified the milestones: 4.5.0, 4.5.1 Nov 15, 2023
@vietj vietj modified the milestones: 4.5.1, 4.5.2 Dec 13, 2023
@vietj vietj modified the milestones: 4.5.2, 4.5.3 Jan 30, 2024
@vietj vietj modified the milestones: 4.5.3, 4.5.4 Feb 6, 2024
@vietj vietj modified the milestones: 4.5.4, 4.5.5 Feb 22, 2024
@vietj vietj modified the milestones: 4.5.5, 4.5.6 Mar 14, 2024
@vietj vietj modified the milestones: 4.5.6, 4.5.7, 4.5.8 Mar 21, 2024
@vietj vietj modified the milestones: 4.5.8, 4.5.9 May 24, 2024
@vietj vietj modified the milestones: 4.5.9, 4.5.10 Jul 17, 2024
@vietj vietj modified the milestones: 4.5.10, 4.5.11 Sep 4, 2024
@vietj vietj modified the milestones: 4.5.11, 4.5.12 Nov 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants