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

Exceptions thrown during isMemberSafe() should go into finest level #7904

Conversation

Projects
None yet
1 participant
@jerrinot
Copy link
Contributor

commented Apr 4, 2016

Justification: When there are topology changes then some exceptions are
expected -> the getFutureResult() method should log exceptions
into finest(), not into warn() level.

It's business as usual during partition migration.

Backport of #7902 into maintanance branch.

Exceptions thrown during isMemberSafe() should go into finest level
Justification: When there are topology changes then some exceptions are
expected -> the getFutureResult() method should log exceptions
into finest(), not into warn() level.

It's business as usual during partition migration.

Backport of #7902 into maintanance branch.

@jerrinot jerrinot added this to the 3.6.3 milestone Apr 4, 2016

@jerrinot jerrinot merged commit fb67264 into hazelcast:maintenance-3.x Apr 4, 2016

1 check passed

default 10876 tests run, 39 skipped, 0 failed.
Details
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.