influxdata / influxdata/influxdb

memory allocation limit reached: limit 10000000 bytes, allocated: xxxxxxxx, wanted: xxxxx

Open
#20,293 4 comments 0 reactions 1 assignee Claimed by @rickspencer3 View on GitHub
area/flux
Dominant language
Rust
Stars
31.7k
Forks
3.7k
Avg merge
13h 37m
Merged PRs (30d)
8

Description

__Steps to reproduce:__
1. Happens on any dashboard that queries a lot of data with a simple query
e.g.
`from(bucket: "PLC_Router_Data")
|> range(start: v.timeRangeStart, stop: v.timeRangeStop)
|> filter(fn: (r) => r["_measurement"] == "data")
|> filter(fn: (r) => r["host"] == v.my_PLC_source)
|> filter(fn: (r) => r["_field"] =~ /ress/ and r["_field"] !~ /Application/)
|> group(columns: ["_field"], mode:"by")
|> toFloat()
|> sort(columns: ["_time"], desc: false)`

__Expected behavior:__
I expect that performing the same query on the same dataset for the same duration either results in:
1) The query *always fails* if we are genuinely doing something that consumes massive amounts of memory (it succeeds 50% of the time)
OR
2) The query *always* succeeds if it's not

__Actual behavior:__
Sometimes you get data
![image](https://user-images.githubusercontent.com/69196723/101646699-c3ee9980-3a2f-11eb-8683-e203f916c40a.png)

Sometimes you get the failure
![image](https://user-images.githubusercontent.com/69196723/101646725-cbae3e00-3a2f-11eb-9cc5-cc445ac896f8.png)

__Environment info:__
* InfluxDB 2.0 Cloud

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.