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

[TRACKING ISSUE] Remove listeners sync with the calling thread #448

Closed
hz-devops-test opened this issue Aug 9, 2021 · 0 comments · Fixed by #475
Closed

[TRACKING ISSUE] Remove listeners sync with the calling thread #448

hz-devops-test opened this issue Aug 9, 2021 · 0 comments · Fixed by #475
Assignees
Labels
Source: Internal to-jira Use to create a placeholder Jira issue in Jira APIs Project Type: Defect
Milestone

Comments

@hz-devops-test
Copy link

The tracking issue for the Java side PR.

See hazelcast/hazelcast#19289 for details.


It turns out that there are some services relying on the removal
of a listener on the member when listener is removed from the client.
Example:
Cache listener count is kept per proxy. When listener is removed,
we decrease the listener count from the cache context.
Since listener removal is async, it could be the case that the cache
is destroyed from the calling thread before we decrement the value.
In such cases, we decrement but the incremented value is lost. Therefore,
we can end up with negative values.

The listener derregistration invoctions are not waited. It was
sync but we have changed the behavior as a side affect during
this fix hazelcast/hazelcast#17646

We may solve this only for CacheListener but there could be more
services relying on sync listener removal. Therefore, as a fix,
we wait for invocation answer from the remote.

fixes hazelcast/hazelcast#19269

@mdumandag mdumandag added this to the 5.0 milestone Sep 15, 2021
@mdumandag mdumandag self-assigned this Sep 15, 2021
@mdumandag mdumandag added the to-jira Use to create a placeholder Jira issue in Jira APIs Project label Sep 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Source: Internal to-jira Use to create a placeholder Jira issue in Jira APIs Project Type: Defect
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants