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?
Hi Simon,
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?
Regards,
Nikhil.