Feature #24233
closed
- Category set to Administration/Usability
- Priority changed from Normal to Low
- Target version set to v14.0.0
- Source set to Development
Why does the command need renamed?
So I guess Vikhyat is suggesting an "MDS" command to match those for other daemons, but that wouldn't just be a renamed version of "fs status", because that command only shows the status of one filesystem.
I'm not sure we need a "ceph mds status" though, because if a user is investigating an unhealthy situation they'll always (I think?) know which filesystem it is.
Thanks John and Patrick for the feedback. I think rename is not needed let us get a new command which can give status of all the MDS daemons, like:
- If they all are up all active-active
- If they all are up some active - some standby
- If some up and some down - some active and some standby
- If all are down
something like this but only daemon status nothing else.
- Subject changed from Rename ceph fs status to ceph mds status to Add new command ceph mds status
- Description updated (diff)
Vikhyat Umrao wrote:
Thanks John and Patrick for the feedback. I think rename is not needed let us get a new command which can give status of all the MDS daemons, like:
- If they all are up all active-active
- If they all are up some active - some standby
- If some up and some down - some active and some standby
- If all are down
something like this but only daemon status nothing else.
Why can't this information be from `ceph fs status --format=json`? I'm not really seeing a plus to having a redundant command.
Patrick Donnelly wrote:
Why can't this information be from `ceph fs status --format=json`? I'm not really seeing a plus to having a redundant command.
Thanks for the feedback, Patrick. Sounds good to me. My only motive was to have consistent command view throughout all the daemons but it is okay as "ceph fs status" serve the same purpose.
Closing it.
- Status changed from New to Closed
Also available in: Atom
PDF