Comment 28 for bug 1852502

On Thu, Apr 14, 2022 at 04:29:37AM -0000, nikhil kshirsagar wrote:
> thanks for the suggestion. Upping log level to critical and then back
> after taking the backup has helped avoid the issue. While the workaround
> does work, can we please get some idea of the long term fix, if any, or
> if we simply need to wait for juju 3.0 which would have mongo 4 which
> wouldnt have this issue?

Can Juju do that for us? As in, `juju create-backup` will
automatically up the log level to only log critical issues and then
back down once it's done creating a backup.