|
From: | Paul Cuzner |
Subject: | [Gluster-devel] New project on the Forge - gstatus |
Date: | Sun, 9 Feb 2014 15:30:56 -0500 (EST) |
address@hidden gstatus]# ./gstatus.py
Analysis complete
Cluster Summary:
Version - 3.4.0.44rhs Nodes - 4/ 4 Bricks - 4/ 4 Volumes - 1/ 1
Volume Summary
myvol ONLINE (4/4 bricks online) - Distributed-Replicate
Capacity: 64.53 MiB/19.97 GiB (used,total)
Status Messages
Cluster is healthy, all checks successful
And then if I take a two nodes down, that provide bricks to the same replica set, I see;
Analysis complete
Cluster Summary:
Version - 3.4.0.44rhs Nodes - 2/ 4 Bricks - 2/ 4 Volumes - 0/ 1
Volume Summary
myvol ONLINE_PARTIAL (2/4 bricks online) - Distributed-Replicate
Capacity: 32.27 MiB/9.99 GiB (used,total)
Status Messages
- rhs1-4 is down
- rhs1-2 is down
- Brick rhs1-4:/gluster/brick1 is down/unavailable
- Brick rhs1-2:/gluster/brick1 is down/unavailable
Pretty much all the data for the volume,bricks and nodes, gets mapped into objects within the code so other checks can easily be added for things like
- filesystem type recommendations - not using XFS, or not using LVM ... make a recommendation
- check the brick mount options are correct and best practice
- show volume info in more detail - raw, and usable with a raw vs usable ratio, brick size stats - are they all the same?
- show volume layout (like lsgvt does), illustrating replica set relationships
- you could add a message based on space usage on the brick (high watermark warning, or overpopulated brick - please run rebalance type stuff)
etc etc
- add an option to write the data out in compact form, and then run it at interval through cron to create a log file - the log file could then be picked up by Justin's analytics tool to give volume space usage and component availabilty over time - a bit quick and dirty, I know ;)
[Prev in Thread] | Current Thread | [Next in Thread] |