Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Improve logging coverage and flexibility #30

@tgross

Description

@tgross

In #28, debugging the problem could have been improved by having better logging in the preStart handler. Also, in #28 (comment) @tgross wrote:

It looks like there's a couple spots we could hook in more logging too. The balance of debug vs info has been hard to get right; I'm wondering if we should keep the last N messages of a DEBUG level in a ring log with some mechanism to dump them to stdout even if the instances are logging at INFO.

Because we don't have a persistent daemon for the manage.py this might be easier said than done. We could always just have a file that we truncate if it gets above size N. Or perhaps just move all the logging around replication setup to INFO, although I'm not wild about that solution either.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions