From: Stefan Priebe <s.priebe@profihost.ag>
To: Sage Weil <sage@inktank.com>
Cc: Josh Durgin <josh.durgin@inktank.com>,
Gregory Farnum <greg@inktank.com>,
Alexandre DERUMIER <aderumier@odiso.com>,
ceph-devel@vger.kernel.org, Mark Nelson <mark.nelson@inktank.com>
Subject: Re: speedup ceph / scaling / find the bottleneck
Date: Tue, 03 Jul 2012 20:20:36 +0200 [thread overview]
Message-ID: <4FF337F4.8020004@profihost.ag> (raw)
In-Reply-To: <Pine.LNX.4.64.1207030828240.27608@cobra.newdream.net>
I'm sorry but this is the KVM Host Machine there is no ceph running on
this machine.
If i change the admin socket to:
admin_socket=/var/run/ceph_$name.sock
i don't have any socket at all ;-(
Am 03.07.2012 17:31, schrieb Sage Weil:
> On Tue, 3 Jul 2012, Stefan Priebe - Profihost AG wrote:
>> Hello,
>>
>> Am 02.07.2012 22:30, schrieb Josh Durgin:
>>> If you add admin_socket=/path/to/admin_socket for your client running
>>> qemu (in that client's ceph.conf section or manually in the qemu
>>> command line) you can check that caching is enabled:
>>>
>>> ceph --admin-daemon /path/to/admin_socket show config | grep rbd_cache
>>>
>>> And see statistics it generates (look for cache) with:
>>>
>>> ceph --admin-daemon /path/to/admin_socket perfcounters_dump
>>
>> This doesn't work for me:
>> ceph --admin-daemon /var/run/ceph.sock show config
>> read only got 0 bytes of 4 expected for response length; invalid
>> command?2012-07-03 09:46:57.931821 7fa75d129700 -1 asok(0x8115a0) AdminSocket:
>> request 'show config' not defined
>
> Oh, it's 'config show'. Also, 'help' will list the supported commands.
>
>> Also perfcounters does not show anything:
>> # ceph --admin-daemon /var/run/ceph.sock perfcounters_dump
>> {}
>
> There may be another daemon that tried to attach to the same socket file.
> You might want to set 'admin socket = /var/run/ceph/$name.sock' or
> something similar, or whatever else is necessary to make it a unique file.
>
>> ~]# ceph -v
>> ceph version 0.48argonaut-2-gb576faa
>> (commit:b576faa6f24356f4d3ec7205e298d58659e29c68)
>
> Out of curiousity, what patches are you applying on top of the release?
>
> sage
>
next prev parent reply other threads:[~2012-07-03 18:20 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-29 10:46 speedup ceph / scaling / find the bottleneck Stefan Priebe - Profihost AG
2012-06-29 11:32 ` Alexandre DERUMIER
2012-06-29 11:49 ` Mark Nelson
2012-06-29 13:02 ` Stefan Priebe - Profihost AG
2012-06-29 13:11 ` Stefan Priebe - Profihost AG
2012-06-29 13:16 ` Stefan Priebe - Profihost AG
2012-06-29 13:22 ` Stefan Priebe - Profihost AG
2012-06-29 15:28 ` Sage Weil
2012-06-29 21:18 ` Stefan Priebe
2012-07-01 21:01 ` Stefan Priebe
2012-07-01 21:13 ` Mark Nelson
2012-07-01 21:27 ` Stefan Priebe
2012-07-02 5:02 ` Alexandre DERUMIER
2012-07-02 6:12 ` Stefan Priebe - Profihost AG
2012-07-02 16:51 ` Gregory Farnum
2012-07-02 19:22 ` Stefan Priebe
2012-07-02 20:30 ` Josh Durgin
2012-07-03 4:42 ` Alexandre DERUMIER
2012-07-03 4:42 ` Alexandre DERUMIER
2012-07-03 7:49 ` Stefan Priebe - Profihost AG
2012-07-03 15:31 ` Sage Weil
2012-07-03 18:20 ` Stefan Priebe [this message]
2012-07-05 21:33 ` Gregory Farnum
2012-07-06 3:50 ` Alexandre DERUMIER
2012-07-06 8:54 ` Stefan Priebe
2012-07-06 17:11 ` Gregory Farnum
2012-07-06 18:09 ` Stefan Priebe - Profihost AG
2012-07-06 18:17 ` Gregory Farnum
2012-07-09 18:21 ` Stefan Priebe
2012-07-03 19:16 ` Stefan Priebe
2012-07-02 13:19 ` Stefan Priebe - Profihost AG
2012-06-29 12:33 ` Stefan Priebe - Profihost AG
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=4FF337F4.8020004@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=aderumier@odiso.com \
--cc=ceph-devel@vger.kernel.org \
--cc=greg@inktank.com \
--cc=josh.durgin@inktank.com \
--cc=mark.nelson@inktank.com \
--cc=sage@inktank.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.