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 upSlice bounds out of range during compaction #3957
Comments
gouthamve
added a commit
to gouthamve/tsdb
that referenced
this issue
Mar 14, 2018
gouthamve
referenced this issue
Mar 14, 2018
Merged
Use the right sized byte array for large indexes #301
gouthamve
added a commit
to gouthamve/tsdb
that referenced
this issue
Mar 14, 2018
gouthamve
added a commit
to gouthamve/tsdb
that referenced
this issue
Mar 14, 2018
gouthamve
added a commit
to gouthamve/tsdb
that referenced
this issue
Mar 14, 2018
gouthamve
added a commit
to gouthamve/tsdb
that referenced
this issue
Mar 14, 2018
gouthamve
closed this
in
prometheus/tsdb#301
Mar 14, 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. |
lock
bot
locked and limited conversation to collaborators
Mar 22, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
gebolze commentedMar 14, 2018
What did you do?
Prometheus was running without any noticeable problems for several days. Also block compaction was successful in the past.
What did you expect to see?
What did you see instead? Under which circumstances?
We've noticed a high memory consumption on the server. The server itself has 32GB and prometheus reached about 99% of the available memory the error below appeared in the log and the process terminated.
When restarting the process the same error is logged.
Environment