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.

Sign up for GitHub

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

Publishing timeout to log at WARN and indicate pending nodes #9551

Closed
wants to merge 2 commits into from
Closed

Publishing timeout to log at WARN and indicate pending nodes #9551

wants to merge 2 commits into from

Commits on Feb 3, 2015

  1. Discovery: publishing timeout to log at WARN and indicate pending nodes 

    When the master publishes a new cluster state it waits (by default) for up to 30s for all nodes to respond. If not it continues to process other pending tasks. At the moment, this timeout is logged under DEBUG but it typically represent a serious issue with one or more of the nodes. We should log it in WARN and give the nodes that failed to respond in a timefly fashion
    @bleskes
    bleskes committed Feb 3, 2015
    Copy the full SHA
    8aa7a00 View commit details
    Browse the repository at this point in the history

Commits on Feb 4, 2015

  1. feedback

    @bleskes
    bleskes committed Feb 4, 2015
    Copy the full SHA
    df89079 View commit details
    Browse the repository at this point in the history