Project

General

Profile

Actions

Feature #6732

closed

mon: 'mon_status' should provide as much insight as 'ping'

Added by Joao Eduardo Luis over 10 years ago. Updated about 10 years ago.

Status:
Rejected
Priority:
Low
Category:
Monitor
Target version:
-
% Done:

0%

Source:
Development
Tags:
Backport:
Reviewed:
Affected Versions:
Pull request ID:

Description

'mon_status' is currently providing just a fraction of the information that would be useful to troubleshoot a monitor. Nowadays, and since 'ceph ping' was merged, we can obtain those infos via 'ping'. However, there is no reason why we shouldn't provide the same detail on 'mon_status', besides being redundant.

Anyway, as we're not dropping 'mon_status', better to make it more useful.

Actions #1

Updated by Joao Eduardo Luis about 10 years ago

  • Status changed from New to Rejected

'mon_status' has a different scope than that of 'ping'.

'mon_status' reports on monitor's status, via the ceph tool when there's a quorum ('ceph mon_status') or via the admin socket. This is monitor-specific status and not 'cluster status', which in turn can be obtained via 'ceph -s' (or, 'ceph status').

'ping' reports on healthiness and status. While 'ping' does report extra information, that is information that should be obtainable via other commands to the monitor when the monitor belongs to the quorum (and that's basically cluster healthiness, instead of monitor healthiness), which is beyond the scope of a per-monitor status retrieval.

This ticket is therefore moot.

Actions

Also available in: Atom PDF