From: Mykola Golub <trociny@FreeBSD.org>
To: Sage Weil <sweil@redhat.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: ceph osd df
Date: Sat, 10 Jan 2015 11:31:59 +0200 [thread overview]
Message-ID: <20150110093158.GA2288@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1501051101010.6168@cobra.newdream.net>
On Mon, Jan 05, 2015 at 11:03:40AM -0800, Sage Weil wrote:
> We see a fair number of issues and confusion with OSD utilization and
> unfortunately there is easy way to see a summary of the current OSD
> utilization state. 'ceph pg dump' includes raw data but it not very
> friendly. 'ceph osd tree' shows weights but not actual utilization.
> 'ceph health detail' tells you the nearfull osds but only when they reach
> the warning threshold.
>
> Opened a ticket for a new command that summarizes just the relevant info:
>
> http://tracker.ceph.com/issues/10452
>
> Suggestions welcome. It's a pretty simple implementation (the mon has
> all the info; just need to add the command to present it) so I'm hoping it
> can get into hammer. If anyone is interested in doing the
> implementation that would be great too!
I am interested in implementing this.
Here is my approach, for preliminary review and discussion.
https://github.com/ceph/ceph/pull/3347
Only plane text format is available currently. As both "osd only" and
"tree" outputs look useful I implemented both and added "tree" option
to tell which to choose.
In http://tracker.ceph.com/issues/10452#note-2 Travis Rhoden suggested
to extend 'ceph osd tree' command to provide this data instead, but
I prefer to have many small specialized commands instead of one with
large output. But if other people also think that it is better to add
a '--detail' to osd tree instead of new command, I will change this.
Also, I am not sure I got an idea how standard deviation should be
calculated. Sage's note in 10452:
- standard deviation (of normalized
actual_osd_utilization/crush_weight/reweight value)
I don't see why utilization should be normalized by
reweight/crush_weight ratio? As I understand the goal is to have
utilization be the same for all devices (thus deviation as small as
possible), does not matter what reweight values we have?
Some examples of command output for my dev environments:
% ceph osd df
ID WEIGHT REWEIGHT %UTIL VAR
0 1.00 1.00 18.12 1.00
1 1.00 1.00 18.14 1.00
2 1.00 1.00 18.13 1.00
--
AVG %UTIL: 18.13 MIN/MAX VAR: 1.00/1.00 DEV: 0
% ceph osd df tree
ID WEIGHT REWEIGHT %UTIL VAR NAME
-1 3.00 - 18.13 1.00 root default
-2 3.00 - 18.13 1.00 host zhuzha
0 1.00 1.00 18.12 1.00 osd.0
1 1.00 1.00 18.14 1.00 osd.1
2 1.00 1.00 18.13 1.00 osd.2
--
AVG %UTIL: 18.13 MIN/MAX VAR: 1.00/1.00 DEV: 0
% ceph osd df
ID WEIGHT REWEIGHT %UTIL VAR
0 1.00 1.00 38.15 0.91
1 1.00 1.00 44.15 1.06
2 1.00 1.00 45.66 1.09
3 1.00 1.00 44.15 1.06
4 1.00 0.80 36.82 0.88
--
AVG %UTIL: 41.78 MIN/MAX VAR: 0.88/1.09 DEV: 6.19
% ceph osd df tree
ID WEIGHT REWEIGHT %UTIL VAR NAME
-1 5.00 - 41.78 1.00 root default
-2 1.00 - 38.15 0.91 host osd1
0 1.00 1.00 38.15 0.91 osd.0
-3 1.00 - 44.15 1.06 host osd2
1 1.00 1.00 44.15 1.06 osd.1
-4 1.00 - 45.66 1.09 host osd3
2 1.00 1.00 45.66 1.09 osd.2
-5 1.00 - 44.15 1.06 host osd4
3 1.00 1.00 44.15 1.06 osd.3
-6 1.00 - 36.82 0.88 host osd5
4 1.00 0.80 36.82 0.88 osd.4
--
AVG %UTIL: 41.78 MIN/MAX VAR: 0.88/1.09 DEV: 6.19
--
Mykola Golub
next prev parent reply other threads:[~2015-01-10 9:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-05 19:03 ceph osd df Sage Weil
2015-01-10 9:31 ` Mykola Golub [this message]
2015-01-10 18:39 ` Sage Weil
2015-01-11 16:31 ` Mykola Golub
2015-01-11 17:33 ` Sage Weil
2015-01-12 8:22 ` Mykola Golub
2015-01-16 15:51 ` Mykola Golub
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150110093158.GA2288@gmail.com \
--to=trociny@freebsd.org \
--cc=ceph-devel@vger.kernel.org \
--cc=sweil@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.