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

InitialMembershipEvent fired with empty member list when client async start enabled #14364

Closed
eminn opened this Issue Jan 9, 2019 · 0 comments

Comments

Projects
None yet
3 participants
@eminn
Copy link
Collaborator

eminn commented Jan 9, 2019

The expected behavior is that when the client has a successful connection to the cluster then the initial membership event is fired with the cluster members.

@sancar sancar added this to the 3.11.2 milestone Jan 9, 2019

@sancar sancar self-assigned this Jan 17, 2019

sancar added a commit to sancar/hazelcast that referenced this issue Jan 17, 2019

Fixing initial membership event when client start async
We were firing two events mistaktenly when a client start async.

First event was empty. This pr adds a check for the first event.
If the member list is empty, it means that the initial membership
event did not arrive yet. We don't need to fire an event.

Actual event will come later and delievered to user listener.

fixes hazelcast#14364

sancar added a commit to sancar/hazelcast that referenced this issue Jan 17, 2019

Fixing initial membership event when client start async
We were firing two events mistakenly when a client starts async.

The first event was empty. This pr adds a check for the first event.
If the member list is empty, it means that the initial membership
event did not arrive yet. We don't need to fire an event.

The actual event will come later and delivered to user-listener.

fixes hazelcast#14364

sancar added a commit to sancar/hazelcast that referenced this issue Jan 17, 2019

Fixing initial membership event when client start async
We were firing two events mistakenly when a client starts async.

The first event was empty. This pr adds a check for the first event.
If the member list is empty, it means that the initial membership
event did not arrive yet. We don't need to fire an event.

The actual event will come later and delivered to user-listener.

fixes hazelcast#14364

(cherry picked from commit 83ebe25)

blazember added a commit to blazember/hazelcast that referenced this issue Jan 22, 2019

Fixing initial membership event when client start async
We were firing two events mistakenly when a client starts async.

The first event was empty. This pr adds a check for the first event.
If the member list is empty, it means that the initial membership
event did not arrive yet. We don't need to fire an event.

The actual event will come later and delivered to user-listener.

fixes hazelcast#14364

blazember added a commit to blazember/hazelcast that referenced this issue Jan 22, 2019

Fixing initial membership event when client start async
We were firing two events mistakenly when a client starts async.

The first event was empty. This pr adds a check for the first event.
If the member list is empty, it means that the initial membership
event did not arrive yet. We don't need to fire an event.

The actual event will come later and delivered to user-listener.

fixes hazelcast#14364
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.