-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
request: disable logging #349
Comments
Did you try setting |
Thanks for the pointing to this. |
It means number of subscribers/goroutines that will process the |
Thanks @runabol |
That's fair |
I have to reopen this:
It means - logs retention 7d
And our DB grows indefenetly:
So I can say - option in config doesnt work OR work really slow and can't delete all new logs. |
Try this config option: Line 35 in 4319d73
|
If you check my message above - this option doesn't work
and
|
Sounds like the pruning process is not catching up quickly enough with the amount of logs you're generating per day. I can make the number of records it deletes per cleaning period configurable. Right now it's hard-coded to 1000 I believe. |
If I'm not mistaken - we have about 20 millions of rows per day in DB |
Can you try release 0.1.73? It adds improvements to log shipping -- buffering log messages (up to one second) rather than sending each log line separately. |
For now as I can understand we have such flow:
This makes some problems - if we have a lot of workers and logs I can see more than x millions mesages in the queue logs. As I can see coordinator doesn't pull and save logs in DB in proper time and that means if I press button Logs it shows nothing. And from time to time I have to purge this queue to see logs
Possible options:
The text was updated successfully, but these errors were encountered: