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

Cluster start timeout error for ElasticSearch 6.2.2 #508

Closed
wahlg opened this issue Mar 2, 2018 · 4 comments
Closed

Cluster start timeout error for ElasticSearch 6.2.2 #508

wahlg opened this issue Mar 2, 2018 · 4 comments

Comments

@wahlg
Copy link

wahlg commented Mar 2, 2018

Running Elasticsearch::Extensions::Test::Cluster.start always gives me a timeout error Timeout while waiting for cluster status [green] and [2] nodes. I've tried different numbers of nodes and increasing the timeout.

It seems like the same issue as #371, but I'm using a later version of ElasticSearch (6.2.2 instead of 5.x).

@wahlg
Copy link
Author

wahlg commented Mar 5, 2018

It looks like this was happening because WebMock requests to localhost were disabled. So all the requests to http://localhost:9250/_cluster/health?wait_for_status=green were failing. These issues weren't visible until I enabled DEBUG mode. Setting WebMock to allow localhost for all fixed the issue:

  config.before(:all) do
    WebMock.disable_net_connect! :allow_localhost => true
  end

@wahlg wahlg closed this as completed Mar 5, 2018
@twp88
Copy link

twp88 commented Mar 30, 2018

Hate to be that guy, but I'm also getting the same error, and in my case it's not because of WebMock;
Timeout while waiting for cluster status [green] and [2] nodes
Timeout::Error (execution expired)

I've tried this in a variety of different ways, including changing the number of nodes, but all to no avail.

As above, seems very similar to 371, but in my case I'm running elasticsearch 6.2.3 with ruby 2.5.0 and rails 5.0.6.

@karmi
Copy link
Contributor

karmi commented Apr 25, 2018

Hmm hmm, wondering... With only a single node, the cluster should be green, I'm afraid this might be something like a bootstrap check failing or something like that. Can you run the cluster with the debug option (eg. DEBUG=yes as environment variable), and have a look at the output? It should tell what's wrong with the cluster...

@jarongao
Copy link

We're running into this issue with an update to Ruby 2.4.4, and this fixed our problem: chrisk/fakeweb#57

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

No branches or pull requests

4 participants