-
Notifications
You must be signed in to change notification settings - Fork 218
[BUG] Changelogs not rotating on mfsmaster with CHANGELOG_SAVE_MODE = 0 #621
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.
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
Comments
Thank you, we will investigate this issue. |
I also experienced this issue. Metalogger with Master's On another metalogger instance, |
The issue was located - a fix will be committed soon. |
Any ideas of when this fix will be available as an Ubuntu 24.04 package in the repository? I'm running v4.56.6 and even setting CHANGELOG_SAVE_MODE to 1 doesn't resolve the issue for me. A restart of mfsmaster will force the change logs to rotate but otherwise the changelog.0 file continues to grow and no rotation takes place. Is there perhaps another way to mitigate the issue until the fix is available in the repository? Thanks! |
I was able to build mfsmaster from the latest source (4.57.1-1) and can confirm that the changelog rotation issue has indeed been fixed. Thanks! |
FYI @stevew-Purdue, "Latest source" |
💯 On a new minor release please. I'm needing to restart regularly to rotate the logs which is a bit of a pain. |
I can confirm this bug does exist and is reproducible. |
By the way, the metalogger has the same problem. It is not rotating its change logs. |
I can confirm this bug also effects the metalogger service too. |
Have you read through available documentation, open Github issues and Github Q&A Discussions?
Yes
System information
Your moosefs version and its origin (moosefs.com, packaged by distro, built from source, ...).
4.56.6, moosefs repo
Operating system (distribution) and kernel version.
Debian 12 6.9.7+bpo-amd64
Describe the problem you observed.
I deployed my cluster with
CHANGELOG_SAVE_MODE = 0
, and noticed that thechangelog.0.mfs
file continues to grow. Right now, it's 255GB.This prompted a short investigation into the code to see how rotation is handled. I saw that when change mode is 0, there's a call to the bgsaver
changelog_rotate
method. When it's not 0, the rotation is performed directly in themeta_term
method.I believe the problem may be directly in
bgsaver.c
and there is a chance the bgsaver thread never receives the rotate request. I have not confirmed or tested that.Can you reproduce it? If so, describe how. If not, describe troubleshooting steps you took before opening the issue.
CHANGELOG_SAVE_MODE = 0
changelog.0.mfs
will be present in the/var/lib/mfs
directory along withmetadata.mfs
(written on exit)CHANGELOG_SAVE_MODE = 1
changelog.1.mfs
changelog.0.mfs
changelog.1.mfs
andchangelog.2.mfs
changelog.0.mfs
CHANGELOG_SAVE_MODE = 0
changelog.0.mfs
etc. without rotationchangelog.0.mfs
indefinitelyCHANGELOG_SAVE_MODE = 1
consistently starts rotation againNote: test was performed in a live cluster environment
Include any warning/errors/backtraces from the system logs.
No matches for
meta
changelog
ordata
with warn/error state.The text was updated successfully, but these errors were encountered: