Skip to content

Fail sniff process if no connections opened#54934

Merged
Tim-Brooks merged 1 commit intoelastic:masterfrom
Tim-Brooks:fail_connection_process_if_no_connections
Apr 10, 2020
Merged

Fail sniff process if no connections opened#54934
Tim-Brooks merged 1 commit intoelastic:masterfrom
Tim-Brooks:fail_connection_process_if_no_connections

Conversation

@Tim-Brooks
Copy link
Copy Markdown
Contributor

Currently the remote cluster sniff connection process can succeed even
if no connections are opened. This commit fixes this by failing the
connection process if no connections are successfully opened.

Currently the remote cluster sniff connection process can succeed even
if no connections are opened. This commit fixes this by failing the
connection process if no connections are successfully opened.
@Tim-Brooks Tim-Brooks added >non-issue :Distributed/Network Http and internode communication implementations v8.0.0 v7.8.0 labels Apr 8, 2020
@Tim-Brooks Tim-Brooks requested a review from ywelsch April 8, 2020 03:26
@elasticmachine
Copy link
Copy Markdown
Collaborator

Pinging @elastic/es-distributed (:Distributed/Network)

Copy link
Copy Markdown
Contributor

@ywelsch ywelsch left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How did you find this?

@Tim-Brooks Tim-Brooks merged commit dd72ccb into elastic:master Apr 10, 2020
Tim-Brooks added a commit that referenced this pull request Apr 10, 2020
Currently the remote cluster sniff connection process can succeed even
if no connections are opened. This commit fixes this by failing the
connection process if no connections are successfully opened.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

:Distributed/Network Http and internode communication implementations >non-issue v7.8.0 v8.0.0-alpha1

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants