[CI] ClusterDisruptionIT: Address already in use #29244
Assignees
Labels
:Delivery/Build
Build or test infrastructure
Team:Delivery
Meta label for Delivery team
>test-failure
Triaged test failures from CI
v6.4.1
Comments
DaveCTurner
added
>test-failure
|
Pinging @elastic/es-distributed |
|
Pinging @elastic/es-core-infra |
ywelsch
removed
the
:Distributed Indexing/Distributed
|
I think this fits better under "Test infrastructure" hence the relabeling. |
|
Another recent failure like these: https://internal-ci.elastic.co/job/elastic+x-pack-elasticsearch+5.6+multijob-windows-compatibility/2289/console . |
DaveCTurner
added a commit
to DaveCTurner/elasticsearch
that referenced
this issue
Aug 29, 2018
Today we support a static list of seed hosts in core Elasticsearch, and allow a dynamic list of seed hosts to be provided via a file using the `discovery-file` plugin. In fact the ability to provide a dynamic list of seed hosts is increasingly useful in containerized environments, so this change moves this functionality to core Elasticsearch to avoid the need for a plugin. For BWC purposes the plugin still exists, but does nothing more than issue a warning when it is used. Furthermore, in order to start up nodes in integration tests we currently assign a known port to each node before startup, which unfortunately sometimes fails if another process grabs the selected port in the meantime. By moving the `discovery-file` functionality into the core product we can use it to avoid this race. Relates elastic#29244 Closes elastic#33030
DaveCTurner
added a commit
that referenced
this issue
Aug 30, 2018
Today we support a static list of seed hosts in core Elasticsearch, and allow a dynamic list of seed hosts to be provided via a file using the `discovery-file` plugin. In fact the ability to provide a dynamic list of seed hosts is increasingly useful, so this change moves this functionality to core Elasticsearch to avoid the need for a plugin. Furthermore, in order to start up nodes in integration tests we currently assign a known port to each node before startup, which unfortunately sometimes fails if another process grabs the selected port in the meantime. By moving the `discovery-file` functionality into the core product we can use it to avoid this race. This change also moves the expected path to the file from `$ES_PATH_CONF/discovery-file/unicast_hosts.txt` to `$ES_PATH_CONF/unicast_hosts.txt`. An example of this file is not included in distributions. For BWC purposes the plugin still exists, but does nothing more than create the example file in the old location, and issue a warning when it is used. We also continue to support the old location for the file, but warn about its deprecation. Relates #29244 Closes #33030
DaveCTurner
added a commit
that referenced
this issue
Aug 30, 2018
Today we support a static list of seed hosts in core Elasticsearch, and allow a dynamic list of seed hosts to be provided via a file using the `discovery-file` plugin. In fact the ability to provide a dynamic list of seed hosts is increasingly useful, so this change moves this functionality to core Elasticsearch to avoid the need for a plugin. Furthermore, in order to start up nodes in integration tests we currently assign a known port to each node before startup, which unfortunately sometimes fails if another process grabs the selected port in the meantime. By moving the `discovery-file` functionality into the core product we can use it to avoid this race. This change also moves the expected path to the file from `$ES_PATH_CONF/discovery-file/unicast_hosts.txt` to `$ES_PATH_CONF/unicast_hosts.txt`. An example of this file is not included in distributions. For BWC purposes the plugin still exists, but does nothing more than create the example file in the old location, and issue a warning when it is used. We also continue to support the old location for the file, but warn about its deprecation. Relates #29244 Closes #33030
6 tasks
|
Closing now that we have a plan of attack in #33675. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+6.x+periodic/1703/console failed because it tried to bind to a port that's already in use:
It looks like a fix for this sort of thing went into #9527 but this doesn't seem to be in place any more.
FWIW the reproduction line was:
I checked the worker and there's nothing binding to that port any more.
The text was updated successfully, but these errors were encountered: