Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upPromql won't time-out queries in expandSeriesSet #4289
Comments
jacksontj
added a commit
to jacksontj/prometheus
that referenced
this issue
Jun 19, 2018
juliusv
added a commit
that referenced
this issue
Jun 19, 2018
juliusv
referenced this issue
Jun 19, 2018
Closed
Handle timeouts during PromQL series population #4290
This was referenced Jun 19, 2018
This comment has been minimized.
This comment has been minimized.
|
This doesn't sound right, it shouldn't take 2m just to lookup the index. How many time series do you have? Can you share your config? |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
|
Can you try this on Prometheus 2.3? |
jacksontj
added a commit
to jacksontj/prometheus
that referenced
this issue
Jun 19, 2018
This comment has been minimized.
This comment has been minimized.
|
I was able to reproduce this on master as well (just finished testing there). |
This comment has been minimized.
This comment has been minimized.
|
So let's say you had 10MM series, with 2h blocks you'd then be doing 10MM*(24/2)*5 = 600MM series lookups, and using a regex matcher. Doesn't sound too surprising to me that that could take >2m. Unless each series lookup is <.2 microseconds. |
This comment has been minimized.
This comment has been minimized.
|
I can see that (though there's more time than that due to compaction). |
brian-brazil
closed this
in
#4291
Jun 21, 2018
brian-brazil
added a commit
that referenced
this issue
Jun 21, 2018
jacksontj
added a commit
to jacksontj/prometheus
that referenced
this issue
Jun 28, 2018
brian-brazil
added a commit
that referenced
this issue
Jul 11, 2018
mknapphrt
added a commit
to mknapphrt/prometheus
that referenced
this issue
Jul 26, 2018
gouthamve
added a commit
to gouthamve/prometheus
that referenced
this issue
Aug 1, 2018
bobmshannon
pushed a commit
to bobmshannon/prometheus
that referenced
this issue
Nov 19, 2018
This comment has been minimized.
This comment has been minimized.
lock
bot
commented
Mar 22, 2019
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
jacksontj commentedJun 19, 2018
Bug Report
What did you do?
Someone sent a large query such as
{__name__=~".+"}[5d]to our prometheus host.What did you expect to see?
I expect the query to timeout before completing, while consuming some memory and CPU along the way.
What did you see instead? Under which circumstances?
The query runs until it exhausts all available memory on the host and OOM killer get is. I have set it up in a repro env locally and the query has been running for ~60m (its still going) even though I have the timeout set to the default 2m.
Environment
2.2
Same symptoms as #4288