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 #4457

Closed
yifangl opened this issue Aug 15, 2022 · 1 comment
Closed

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

yifangl opened this issue Aug 15, 2022 · 1 comment

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());

Do you have a reproducer?

This is currently in our private repo so cannot paste the reproducer here. But we are just using the basic get() method. It should be reproduced by setting up a zk-based AsyncMap and call get() on a periodic basis. (Our use case calls it every 5 sec.)

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

@yifangl yifangl added the bug label Aug 15, 2022
@vietj vietj closed this as completed Aug 16, 2022
@vietj
Copy link
Member

vietj commented Aug 16, 2022

see vert-x3/vertx-zookeeper#129

@vietj vietj removed the bug label Aug 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants