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

HazelcastClient recovery #218

Closed
alexite opened this issue Jul 26, 2012 · 1 comment

Comments

Projects
None yet
2 participants
@alexite
Copy link

commented Jul 26, 2012

Hi Fuad,
I'm working with hazel cast client and saw that if I create a client and don't use it while remote cache is down, then I can use the same client after remote cache is up again.
However, if I'm trying to access the cache using client while the cache is not available, then this client cannot be used anymore even after server becomes available again.
My question is what is the best way to manage clients?
today I simply implemented MembershipListener and on MemeberRemoved event check if there is available clients using HazelcastClient.getAllHazelcastClients(), then set indication that remote cache is not available,
and in MemberAdded event I check if cache was not available, then I create a new client.
But may be there is more elegant way to manage client/server availability?

Thanks,
Alex.

@fuadm

This comment has been minimized.

Copy link
Member

commented Aug 13, 2012

This is fixed now in master.

@fuadm fuadm closed this Aug 13, 2012

@ghost ghost assigned fuadm Aug 13, 2012

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.