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 upMake logging about suspended ingestion less spammy (and more meaningful). #1269
Comments
This comment has been minimized.
This comment has been minimized.
|
Storage logging can be very noisy. There's a high number of operations and Generally it has not reached a degree where it would be inhibiting the On Fri, Dec 18, 2015 at 10:46 AM Filippo Giunchedi notifications@github.com
|
This comment has been minimized.
This comment has been minimized.
|
thanks for the quick reply @fabxc ! yeah it hasn't been generally a problem during normal server operations. I suppose because the chunks to persist normally are not very close to thanks! |
This comment has been minimized.
This comment has been minimized.
|
The reason for the many lag messages is that every target logs it separately. While that's mildly annoying, it's not really a problem. And it mirrors the fact that every target is suspended and resumed separately. Also, take into account that suspension of ingestion is a highly irregular state. If it happens regularly, you are either overloading your server, or you need to tweak flags. It's definitely a sign you should be very worried about. From that perspective, "spamming" the logs is not the worst that can happen. |
beorn7
added
the
enhancement
label
Dec 18, 2015
This comment has been minimized.
This comment has been minimized.
|
thanks @beorn7! that prompted me to look and indeed |
This comment has been minimized.
This comment has been minimized.
|
Observing More RAM usage helps to boos performance here, so increase |
beorn7
changed the title
log spam while persisting chunks on startup
Make logging about suspended ingestion less spammy (and more meaningful).
Dec 18, 2015
This comment has been minimized.
This comment has been minimized.
|
This is fixed in master. |
beorn7
closed this
Feb 3, 2016
This comment has been minimized.
This comment has been minimized.
lock
bot
commented
Mar 24, 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. |
filippog commentedDec 18, 2015
hi!
I'm trying prometheus 0.16.1 with go 1.5.1 from Debian stretch for evaluation purposes. After a restart if chunks are detected to need persistance there seems to be ping-pong going on with log messages and resulting spam until persistent chunks fall under the watermark.
sometimes large spams of
Sample ingestion resumedwould appear too