Description of problem: When the MDS detects that the mds-mon connection is laggy due to missing beacon acks, it spams the debug log with "is_laggy" messages at level 1: > 2018-08-31 07:15:26.991594 7f6209c1d700 1 mds.beacon.storagem4-ngn1 is_laggy 15.000025 > 15 since last acked beacon > 2018-08-31 07:15:26.991602 7f6209c1d700 1 mds.beacon.storagem4-ngn1 is_laggy 15.000032 > 15 since last acked beacon > 2018-08-31 07:15:26.991603 7f6209c1d700 1 mds.beacon.storagem4-ngn1 is_laggy 15.000034 > 15 since last acked beacon > 2018-08-31 07:15:26.991633 7f6209c1d700 1 mds.beacon.storagem4-ngn1 is_laggy 15.000063 > 15 since last acked beacon > 2018-08-31 07:15:26.991641 7f6209c1d700 1 mds.beacon.storagem4-ngn1 is_laggy 15.000071 > 15 since last acked beacon How reproducible: 100% when connection with mons is partitioned.
Created attachment 1481699 [details] Hotfix_1624527_report Hotfix_1624527_report
*** Bug 1626912 has been marked as a duplicate of this bug. ***
Manual Testing of Hotfix is completed. Yet to get Automation CI results from shreekar, as of now 3 -4 tests are pending, so far no failures observed. Shreekar will update the CI run link once automation is complete.
Thanks Patrick. Moving this bug to verified.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:3530