Skip to content
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

mds: print mdsmap processed at low debug level #23061

Merged
merged 1 commit into from
Jul 21, 2018
Merged

Conversation

batrick
Copy link
Member

@batrick batrick commented Jul 15, 2018

Production deployments use low debugging but it'd be useful to always know what
MDSMap epoch the MDS is currently processing. (In the case of skipped epochs or
unsynchronized processing.)

Fixes: https://tracker.ceph.com/issues/24852

Signed-off-by: Patrick Donnelly pdonnell@redhat.com

@jcsp
Copy link
Contributor

jcsp commented Jul 16, 2018

This is reasonable, given how rarely the MDSMap changes.

Since the default log levels are mainly reserved for warnings and errors, it might be good to rephrase this a bit to make it clearer to the uninitiated that it's nothing to worry about, like "Updated to MDS map version X". It's less direct phrasing, but that's perhaps the cost of doing business for log messages that are going to be in front of end user eyeballs by default.

Production deployments use low debugging but it'd be useful to always know what
MDSMap epoch the MDS is currently processing. (In the case of skipped epochs or
unsynchronized processing.)

Fixes: https://tracker.ceph.com/issues/24852

Signed-off-by: Patrick Donnelly <pdonnell@redhat.com>
@batrick
Copy link
Member Author

batrick commented Jul 16, 2018

That's a good point. Thanks @jcsp and updated.

@batrick
Copy link
Member Author

batrick commented Jul 16, 2018

retest this please

@batrick batrick merged commit 3820cf8 into ceph:master Jul 21, 2018
batrick added a commit that referenced this pull request Jul 21, 2018
* refs/pull/23061/head:
	mds: print mdsmap processed at low debug level

Reviewed-by: John Spray <john.spray@redhat.com>
@batrick batrick deleted the i24852 branch July 24, 2018 19:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants