Bug #8337: Logging too verbose in handle_client_file_setlock - CephFS - Ceph

Actions

Copy link

Bug #8337

closed

Logging too verbose in handle_client_file_setlock

Added by Markus Blank-Burian almost 10 years ago. Updated over 7 years ago.

Status:

Resolved

Priority:

Normal

Assignee:

Category:

Target version:

% Done:

Source:

Community (user)

Tags:

Backport:

Regression:

Severity:

3 - minor

Reviewed:

Affected Versions:

ceph-qa-suite:

Component(FS):

Labels (FS):

Pull request ID:

Crash signature (v1):

Crash signature (v2):

Description

Each time, a client uses fcntl locking, the mds server writes a log message with loglevel 0. This results in quite a lot of cpu activity and disk usage with our workload and therefore logging had to be disabled setting "debug mds -1". Since this message is pure informational, its level should be much higher.

2014-05-11 21:52:57.730147 7fb0d52a1700 0 mds.0.server handle_client_file_setlock: start: 0, length: 0, client: 2921266, owner: 18222, pid: 18446612183967482112, type: 1

2014-05-11 21:52:57.745604 7fb0d52a1700 0 mds.0.server handle_client_file_setlock: start: 0, length: 0, client: 2921266, owner: 18222, pid: 18446612183967482112, type: 2