search

elastic / elasticsearch-migration

This plugin will help you to check whether you can upgrade directly to the next major version of Elasticsearch, or whether you need to make changes to your data and cluster before doing so.
290 stars 32 forks source link

misleading output when blocked by a proxy #49

Closed ynux closed 8 years ago

ynux commented 8 years ago

We run our cluster behind a proxy which is allowing only specified requests (kibana and kopf read-only). This results in strange behaviour of the migration tool. It comes back red, marking all indices as closed. Some were closed, in fact. So I ran it with "Ignore closed indices". This resulted in a green migration tool, and it skipped all indexes. Another attempt with all indices opened had the same result. Only removing the proxy helped. I suggest: A - When the tool receives a HTML 404, it shows it; B - A set of simple curl scripts checking for conflicts etc that can be run from the command line, for environments where people cannot change the proxy configuration.

clintongormley commented 8 years ago

When the tool receives a HTML 404, it shows it;

This should work in the 2.x tool

B - A set of simple curl scripts checking for conflicts etc that can be run from the command line, for environments where people cannot change the proxy configuration.

Given that the plugin is implemented in a significant amount of JS, it would not be trivial to replicate in curl.