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

Client disconnect leads to stucked clusterExecutor shutdown (3.6.2) #8721

Closed
uladzimirFilipchanka opened this issue Aug 15, 2016 · 0 comments · Fixed by #9508
Closed

Client disconnect leads to stucked clusterExecutor shutdown (3.6.2) #8721

uladzimirFilipchanka opened this issue Aug 15, 2016 · 0 comments · Fixed by #9508
Assignees
Milestone

Comments

@uladzimirFilipchanka
Copy link

I have two apps deployed on different VM's. First app connects to another as Hazelcast Client.
As soon second app goes down, client starts reconnection as expeced. Finally the client says

"Could not re-connect to cluster shutting down the client"

and goes to ClusterListenerSupport:233 to shutdown LifecycleService.

After some components shutdowns, called ClusterListenerSupport.shutdown
And the component tries to shutdown clusterExecutor and stucked for TERMINATE_TIMEOUT_SECONDS because the task is launched inside this clusterExecutor.

Here is screen from debug view
b2008d0b19

Log says:

13:34:41,955 INFO com.hazelcast.core.LifecycleService HazelcastClient[hz.client_50_ustaxi-shift][3.6.2] is SHUTTING_DOWN
13:35:11,957 WARNING com.hazelcast.client.spi.impl.ClusterListenerSupport cluster executor awaitTermination could not completed in 30 seconds
13:35:11,960 INFO com.hazelcast.core.LifecycleService HazelcastClient[hz.client_50_ustaxi-shift][3.6.2] is SHUTDOWN

This issue reproduces permanently and only after target instance goes down.

@jerrinot jerrinot added this to the 3.7.1 milestone Aug 15, 2016
@jerrinot jerrinot modified the milestones: 3.7.1, 3.7.2 Aug 29, 2016
@degerhz degerhz modified the milestones: 3.7.3, 3.7.2 Sep 23, 2016
@ihsandemir ihsandemir modified the milestones: 3.7.4, 3.7.3 Nov 1, 2016
@sancar sancar modified the milestones: 3.7.5, 3.7.4 Nov 29, 2016
@sancar sancar self-assigned this Dec 21, 2016
sancar pushed a commit to sancar/hazelcast that referenced this issue Dec 21, 2016
Launch a new thread when client needs to be closed from cluster
thread.

fixes hazelcast#8721
sancar pushed a commit to sancar/hazelcast that referenced this issue Dec 21, 2016
Launch a new thread when client needs to be closed from cluster
thread.

fixes hazelcast#8721
sancar pushed a commit to sancar/hazelcast that referenced this issue Dec 21, 2016
Launch a new thread when client needs to be closed from cluster
thread.

fixes hazelcast#8721
sancar pushed a commit to sancar/hazelcast that referenced this issue Dec 21, 2016
Launch a new thread when client needs to be closed from cluster
thread.

fixes hazelcast#8721
sancar pushed a commit to sancar/hazelcast that referenced this issue Dec 23, 2016
Launch a new thread when client needs to be closed from cluster
thread.

fixes hazelcast#8721
sancar pushed a commit to sancar/hazelcast that referenced this issue Dec 23, 2016
Launch a new thread when client needs to be closed from cluster
thread.

fixes hazelcast#8721
sancar pushed a commit to sancar/hazelcast that referenced this issue Dec 23, 2016
Launch a new thread when client needs to be closed from cluster
thread.

fixes hazelcast#8721
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants