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

Jump to bottom

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

Merged
merged 1 commit into from Apr 4, 2016
Merged

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

merged 1 commit into from Apr 4, 2016

Commits on Apr 4, 2016

  1. 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 hazelcast#7902 into maintanance branch.
    @jerrinot
    jerrinot committed Apr 4, 2016
    Copy the full SHA
    77262a9 View commit details
    Browse the repository at this point in the history