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

Timelion returns inconsistent results when elasticsearch.shardTimeout is set to 0 #23428

Closed
ismael-hasan opened this Issue Sep 24, 2018 · 1 comment

Comments

Projects
None yet
4 participants
@ismael-hasan
Copy link
Member

ismael-hasan commented Sep 24, 2018

Kibana version: 6.4.0

Elasticsearch version: 6.4.0

Describe the bug:
the parameter elasticsearch.shardTimeout defines the timeout of the queries sent to Elasticsearch from Kibana (kibana settings) :

Default: 30000 Time in milliseconds for Elasticsearch to wait for responses from shards. Set to 0 to disable.

This parameter started to be considered in Timelion in 6.4 - #19711

When it is set to 0, the same timelion query, in the same interval of data (static) returns different graphs. When setting the value large enough so the query completes, results are consistent.

Steps to reproduce:

  1. Create indices big enough so timelion queries are expensive
  2. Set the following properties - only the shard timeout should be needed, but in the test the other 2 were also included
elasticsearch.pingTimeout: 30000
elasticsearch.requestTimeout: 45000
elasticsearch.shardTimeout: 0
  1. Create an expensive multisearch timelion query (across several big indices)
  2. Run the query in a fixed time interval, and auto-refresh.
  3. The different executions provide different charts.

Expected behavior:
All of the executions provide the same chart. Setting elasticsearch.shardTimeout to the default 30000 provided consistency across executions

@waynetaylor

This comment has been minimized.

Copy link

waynetaylor commented Sep 24, 2018

+1 to this.. Look like we have same issue. I raised Case 262127 for it to support.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.