Project

General

Profile

Actions

Bug #10546

closed

ceph time check start round bug in monitor.cc

Added by eyun xu over 9 years ago. Updated about 9 years ago.

Status:
Resolved
Priority:
High
Category:
Monitor
Target version:
-
% Done:

0%

Source:
Community (user)
Tags:
Backport:
giant,firefly
Regression:
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

HI all,

My ceph cluster report clock skew even after time syncing 30min ago, so i'm digging in the src code of ceph0.80.6,
i think the following code in void Monitor::timecheck_start_round() in monitor.cc from line 3160 to 3168 is very strange,

in my opinion, the highligted part should be curr_time - timecheck_round_start < max ,

that is: if time elapsed less than max, then keep current round going, else cancel current round.

double max = g_conf->mon_timecheck_interval*3;
if (curr_time - timecheck_round_start > max) {
dout(10) << func << " keep current round going" << dendl;
goto out;
} else {
dout(10) << func
<< " finish current timecheck and start new" << dendl;
timecheck_cancel_round();
}

just my opinion, any reply is welcomed!

thanks very much

Actions #1

Updated by Sage Weil about 9 years ago

  • Assignee set to Joao Eduardo Luis
  • Source changed from other to Community (user)
Actions #2

Updated by Joao Eduardo Luis about 9 years ago

  • Category set to Monitor
  • Status changed from New to Fix Under Review
Actions #3

Updated by Sage Weil about 9 years ago

  • Status changed from Fix Under Review to Pending Backport
  • Backport set to giant,firefly
Actions #4

Updated by Loïc Dachary about 9 years ago

  • Severity changed from 1 - critical to 3 - minor
Actions #5

Updated by Loïc Dachary about 9 years ago

  • Description updated (diff)
Actions #8

Updated by Sage Weil about 9 years ago

  • Status changed from Pending Backport to Resolved
Actions

Also available in: Atom PDF