Kibana4 version check is failing

[bradvido]

I have upgraded my ES cluster to 1.4.0.Beta1, but Kibana4 is complaining with:
This version of Kibana requires at least Elasticsearch 1.4.0.Beta1

I do have multiple other non-data nodes in my cluster which are not upgraded to 1.4.0. Could that cause the check to fail? I added a comment to the line in this commit: 98bb102

Also, I see some logic in the version check trying to ignore beta tags. It "skips everything after the '-'", but I noticed that the Beta1 tag is not separated by a '-', it's just a '.' separating it from the version num.

Bonus points: It would be useful if the error message spit out what Node & version caused the check to fail.

[spalger]

The check currently runs against all nodes in the cluster, including non-data nodes. I like the idea of stating which nodes caused the failure.

Couldn't updating only part of the cluster cause issues? I'm not sure...

[rashidkpc]

This is by design, we require all nodes to be at least 1.4.0, including non-data nodes, as Kibana itself may be connected to a non-data node. Agree it would be nice to list the non-conforming nodes would be a nice addition. Feel free to open a feature request ticket if you feel it is important enough.

[arohter]

Can you elaborate a bit on which ES 1.4 -only features kibana4 uses? We've got some folks here dying to try it out, but we're not going to upgrade our clusters to ES 1.4 while it's still so young.

[CullyB]

I'm curious about this as well; from what I understood 1.4 is less about new features and more about cluster stability

On Oct 6, 2014, at 4:43 PM, arohter notifications@github.com wrote:

Can you elaborate a bit on which ES 1.4 -only features kibana4 uses? We've got some folks here dying to try it out, but we're not going to upgrade our clusters to ES 1.4 while it's still this young.

—
Reply to this email directly or view it on GitHub.

[bradvido]

I don't get it. I'm prevented from using Kibana 4 on my cluster because I have a Logstash client sending data via the elasticsearch output (and it's an earlier version than the cluster). This is all on a test/dev cluster, and the backwards compatibility is great for ES.

Doesn't make sense to me. I'd prefer a warn and continue approach here.

I know that i can change logstash to use http output, but that's not the point; it's just an example.

I ended up editing the index.js file inside the jar to always return true for the version check and Kibana 4 is working flawlessly so far.