You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Install mongosh on host machine in case of LXD or copy your data set into juju unit
Using "charmed-mongodb.mongoimport" (from inside of juju unit) or mongoimport (from host machine) start import data
Periodically check free space on disk.
Expected behavior
Import of 70 GB of data should not consume 500+GB of disk space
Actual behavior
Disk space is being consumed very quickly. This most likely happens due to audit logs.
Log rotation and allowing users to opt out from audit logging should solve the problem
Versions
stable/164
Operating system:
Juju CLI:
Juju agent:
Charm revision:
LXD:
Log output
Juju debug log:
Additional context
The text was updated successfully, but these errors were encountered:
## Issue
[ISSUE-398](#398)
At the current moment Charmed MongoDB logs, can grow very fast,
especially audit log.
For example when a user imports data sets.
## Solution
Support log rotation to avoid consuming too much space with log files.
Log will be rotated if they grow bigger than 100M, the check for log
files size will be performed every minute
## Result of log rotation
<img width="635" alt="Screenshot 2024-04-23 at 18 59 47"
src="https://github.com/canonical/mongodb-operator/assets/132273757/c1ccbd81-ca9d-4678-9423-0f2374f7226d">
Steps to reproduce
Expected behavior
Import of 70 GB of data should not consume 500+GB of disk space
Actual behavior
Disk space is being consumed very quickly. This most likely happens due to audit logs.
Log rotation and allowing users to opt out from audit logging should solve the problem
Versions
stable/164
Operating system:
Juju CLI:
Juju agent:
Charm revision:
LXD:
Log output
Juju debug log:
Additional context
The text was updated successfully, but these errors were encountered: