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

Logstash using protocol => "node" prevents Kibana from finding correct version of ES #1572

Closed
jpbriend opened this issue Oct 7, 2014 · 1 comment

Comments

@jpbriend
Copy link

jpbriend commented Oct 7, 2014

I installed a fresh new ES version 1.4.0.Beta 1.
Without Logstash plugged in, Kibana checks correctly the ES version.

As soon as I plug a Logstash configured with ES plugin and protocol => 'node', Kibana is blocking on the ES version not seen as 1.4.0.Beta1.
If I configure protocol to be 'http', everything is fine.

@bradvido
Copy link

bradvido commented Oct 7, 2014

Yes, I brought that up here #1546
It's considered not a bug and all nodes (data or client) connected to your cluster must be >= 1.4.

You can work around it by editing line 39666 of the index.js file (inside the jar -- use 7zip to update inside the jar file).
I changed it
from:
if ( versionmath.is('>=' + minimumElasticsearchVersion, versions)) return true;
to:
if (true /*edited*/ || versionmath.is('>=' + minimumElasticsearchVersion, versions)) return true;

Kibana 4 is working great for me even with non-data nodes being an earlier version of ES, but your mileage may vary.

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

2 participants