Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Excessive log messages #1154

Open
abh opened this issue Aug 23, 2019 · 1 comment
Open

Excessive log messages #1154

abh opened this issue Aug 23, 2019 · 1 comment

Comments

@abh
Copy link

abh commented Aug 23, 2019

During normal operation the logs are very noisy with low value information. I was going to see if I could change the log level (we use the Postgres operator), but at a glance the important messages (secondary/leader swapping) are also logged with the INFO log level...

2019-08-23 05:50:08,234 INFO: Lock owner: ask-pg-1; I am ask-pg-0
2019-08-23 05:50:08,234 INFO: does not have lock
2019-08-23 05:50:08,253 INFO: no action.  i am a secondary and i am following a leader
2019-08-23 05:50:18,183 INFO: Lock owner: ask-pg-1; I am ask-pg-0
2019-08-23 05:50:18,183 INFO: does not have lock
2019-08-23 05:50:18,211 INFO: no action.  i am a secondary and i am following a leader
@kmoppel
Copy link
Contributor

kmoppel commented Aug 23, 2019

+1. Agree, messages as "INFO: promoted self to leader by acquiring session lock" could be WARNING.

One idea would be also to store information on last (some X entries, not to burden) switchovers in DCS...just like repmgr has it. One can of course already use the on_role_change hook, but that needs configuring which is an extra hurdle.

@CyberDem0n CyberDem0n mentioned this issue Dec 15, 2020
Closed
@mcassaniti mcassaniti mentioned this issue Oct 27, 2022
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

logging: Log no action messages at debug level
2 participants
@abh @kmoppel