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 upLarge chunks #3993
Comments
This comment has been minimized.
This comment has been minimized.
|
Hi could you upgrade to |
This comment has been minimized.
This comment has been minimized.
|
Hi, I did already but the data still there. Will I need to delete them or is prometheus able to purge this? |
This comment has been minimized.
This comment has been minimized.
|
You will need to delete them. |
This comment has been minimized.
This comment has been minimized.
|
I will reopen if the issue comes back. Thanks |
matejkramny
closed this
Mar 21, 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.
matejkramny commentedMar 21, 2018
What did you do?
nothing / n/a
What did you expect to see?
Reasonable usage of disk space
What did you see instead? Under which circumstances?
Disk space usage by prometheus grew substantially.
Environment
Docker, prometheus v2.2.0
System information:
insert output of
uname -srmhereLinux 4.13.0-37-generic x86_64
Prometheus version:
insert output of
prometheus --versionhere2.2.0
Logs don't show any relevant information. I found a maybe-related issue #3190 however there are no .tmp files, and i don't see any "compaction failed" in the logs.
The logs are normal, aside from occasional scrape failures.
Can something be done about the size of the chunks? It seems unreasonable to me to grow like that (see graph)