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

feat(cluster) record and log errors causing nodes to be marked as DOWN #129

Merged
merged 1 commit into from
May 9, 2019

Conversation

thibaultcha
Copy link
Owner

This updates the host still considered down error logs to include the
error causing the node to be down, as well as the duration for which it
will still be considered down. E.g.:

all hosts tried for query failed. 127.0.0.1: host still considered
down for 1s (last error: timeout). 127.0.0.2: host still considered
down for 1s (last error: timeout)

@thibaultcha thibaultcha force-pushed the feat/record-down-errors branch from de1cf55 to b70e265 Compare May 8, 2019 17:37
This updates the `host still considered down` error logs to include the
error causing the node to be down, as well as the duration for which it
will still be considered down. E.g.:

    all hosts tried for query failed. 127.0.0.1: host still considered
    down for 1s (last error: timeout). 127.0.0.2: host still considered
    down for 1s (last error: timeout)
@thibaultcha thibaultcha force-pushed the feat/record-down-errors branch from b70e265 to 35d5865 Compare May 8, 2019 17:58
@thibaultcha thibaultcha merged commit a546705 into master May 9, 2019
@thibaultcha thibaultcha deleted the feat/record-down-errors branch May 9, 2019 19:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant