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

Kibana 4 doesn't properly recognize elasticsearch version when logstash workers are connected #1636

Closed
Baramin opened this issue Oct 10, 2014 · 1 comment

Comments

@Baramin
Copy link

Baramin commented Oct 10, 2014

Hi,

When Kibana 4 gets node list from elasticsearch, it looks like it doesn't appreciate seing logstash workers announcing their v1.1.1.

I need to stop logstash, start kibana and navigate the GUI for it to work properly. I can then start logstash.

With logstash running, I get the following error from Kibana :

Fatal Error
This version of Kibana requires at least Elasticsearch 1.4.0.Beta1

SetupError@http://myserver:5601/index.js:39486:51
checkEsVersion/<@http://myserver:5601/index.js:39667:14
qFactory/defer/deferred.promise.then/wrappedCallback@http://myserver:5601/index.js:20763:15
qFactory/ref/<.then/<@http://myserver:5601/index.js:20849:11
$RootScopeProvider/this.$get</Scope.prototype.$eval@http://myserver:5601/index.js:21892:9
$RootScopeProvider/this.$get</Scope.prototype.$digest@http://myserver:5601/index.js:21704:15
$RootScopeProvider/this.$get</Scope.prototype.$apply@http://myserver:5601/index.js:21996:13
done@http://myserver:5601/index.js:17569:34
completeRequest@http://myserver:5601/index.js:17783:7
createHttpBackend/</xhr.onreadystatechange@http://myserver:5601/index.js:17726:1

If I stop logstash, it works as intended.

@rashidkpc
Copy link
Contributor

This is because we require all nodes in the cluster to be at least 1.4.0.Beta1, since it is possible for requests to end up at any node. Logstash's elasticsearch output actually creates an Elasticsearch node. There's really no one to differentiate between logstash nodes and other nodes. The workaround here is to use logstash's elasticsearch-http output.

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