Kibana: Kibana still spamming logs when different version from Elasticsearch

Created on 18 Oct 2017 · 3Comments · Source: elastic/kibana

I thought maybe it was resolved by this PR:

https://github.com/elastic/kibana/pull/8865

But I am still seeing this message printed every few seconds (Kibana 5.4.3 talking to ES 5.6.3). it isn't possible to upgrade since the kibana plugin I'm using is only written against 5.4.3.

{"type":"log","@timestamp":"2017-10-18T04:52:25Z","tags":["warning"],"pid":1,"kibanaVersion":"5.4.3","nodes":[{"version":"5.6.3","http":{"publish_address":"10.43.188.45:18923"},"ip":"10.43.188.45"},{"version":"5.6.3","http":{"publish_address":"172.25.69.187:18281"},"ip":"172.25.69.187"},{"version":"5.6.3","http":{"publish_address":"10.232.131.86:18308"},"ip":"10.232.131.86"}],"message":"You're running Kibana 5.4.3 with some different versions of Elasticsearch. Update Kibana or Elasticsearch to the same version to prevent compatibility issues: v5.6.3 @ 10.43.188.45:18923 (10.43.188.45), v5.6.3 @ 172.25.69.187:18281 (172.25.69.187), v5.6.3 @ 10.232.131.86:18308 (10.232.131.86)"}

{"type":"log","@timestamp":"2017-10-18T04:52:27Z","tags":["warning"],"pid":1,"kibanaVersion":"5.4.3","nodes":[{"version":"5.6.3","http":{"publish_address":"172.25.69.187:18281"},"ip":"172.25.69.187"},{"version":"5.6.3","http":{"publish_address":"10.43.188.45:18923"},"ip":"10.43.188.45"},{"version":"5.6.3","http":{"publish_address":"10.232.131.86:18308"},"ip":"10.232.131.86"}],"message":"You're running Kibana 5.4.3 with some different versions of Elasticsearch. Update Kibana or Elasticsearch to the same version to prevent compatibility issues: v5.6.3 @ 172.25.69.187:18281 (172.25.69.187), v5.6.3 @ 10.43.188.45:18923 (10.43.188.45), v5.6.3 @ 10.232.131.86:18308 (10.232.131.86)"}

{"type":"log","@timestamp":"2017-10-18T04:52:32Z","tags":["warning"],"pid":1,"kibanaVersion":"5.4.3","nodes":[{"version":"5.6.3","http":{"publish_address":"10.43.188.45:18923"},"ip":"10.43.188.45"},{"version":"5.6.3","http":{"publish_address":"172.25.69.187:18281"},"ip":"172.25.69.187"},{"version":"5.6.3","http":{"publish_address":"10.232.131.86:18308"},"ip":"10.232.131.86"}],"message":"You're running Kibana 5.4.3 with some different versions of Elasticsearch. Update Kibana or Elasticsearch to the same version to prevent compatibility issues: v5.6.3 @ 10.43.188.45:18923 (10.43.188.45), v5.6.3 @ 172.25.69.187:18281 (172.25.69.187), v5.6.3 @ 10.232.131.86:18308 (10.232.131.86)"}

Operations

Source

ctindel

Most helpful comment

+1 Still an issue in later 6.4.3 version:

Apart from this being a spamming issue (for example, I am sampling 10K lines from a multiple Gb Kibana log file where 9800+ lines are these compatibility messages), the message is also contradictory to our support matrix where we indicate that patch versions of Kibana <-> ES are compatible (e.g., Kibana 6.4.x is compatible with ES 6.4.x).

{"type":"log","@timestamp":"2018-11-21T10:10:30Z","tags":["warning"],"pid":2613,"kibanaVersion":"6.4.3","nodes":[{"version":"6.4.0","http":{"publish_address":"IP:9200"},"ip":"IP"}],"message":"You're running Kibana 6.4.3 with some different versions of Elasticsearch. Update Kibana or Elasticsearch to the same version to prevent compatibility issues: v6.4.0 @ IP:9200 (IP)"}

ppf2 on 21 Nov 2018

👍2

All 3 comments

+1 Still an issue in later 6.4.3 version:

{"type":"log","@timestamp":"2018-11-21T10:10:30Z","tags":["warning"],"pid":2613,"kibanaVersion":"6.4.3","nodes":[{"version":"6.4.0","http":{"publish_address":"IP:9200"},"ip":"IP"}],"message":"You're running Kibana 6.4.3 with some different versions of Elasticsearch. Update Kibana or Elasticsearch to the same version to prevent compatibility issues: v6.4.0 @ IP:9200 (IP)"}

ppf2 on 21 Nov 2018

👍2

I can confirm this bug. It seems like #8865 assumes a stable ordering of nodes from the ES nodes API when determining if a log message had been seen before. When Elasticsearch returns a different node ordering from the _nodes API we end up logging up to N duplicate messages (where N is the amount of ES nodes).