Thank you, Gandalf and Igor. I intuitively think that building a cluster on
another is not appropriate. Maybe I should give RadosGW a try first.
On Thu, May 2, 2013 at 3:00 AM, Igor Laskovy wrote:
> Or maybe in case the hosting purposes easier implement RadosGW.
>
--
Yudong Guang
guangyudong
Or maybe in case the hosting purposes easier implement RadosGW.
___
ceph-users mailing list
ceph-users@lists.ceph.com
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
2013/5/1 Yudong Guang :
> The reason why I like block device is that it has the best reading
> performance. But not being able to be shared is a fatal drawback here. Maybe
> I should change some strategy or tuning the ceph fs. My goal is to use a
> cluster to host a lot of small images, each of whi
Thank you, Mike.
The reason why I like block device is that it has the best reading
performance. But not being able to be shared is a fatal drawback here.
Maybe I should change some strategy or tuning the ceph fs. My goal is to
use a cluster to host a lot of small images, each of which is about 17
That is the expected behavior. RBD is emulating a real device, you wouldn't
expect good things to happen if you were to plug the same drive into two
different machines at once (perhaps with some soldering). There is no built in
mechanism for two machines to access the same block device concurr
Hi,
I've been trying to use block device recently. I have a running cluster
with 2 machines and 3 OSDs.
On a client machine, let's say A, I created a rbd image using `rbd create`
, then formatted, mounted and wrote something in it, everything was working
fine.
However, problem occurred when I tr
