Why is running OSDs on a Hypervisors a bad idea?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hey,

We keep hearing that running Hypervisors (KVM) on the OSD nodes is a bad idea. But why exactly is that the case?

In our usecase, under normal operations our VMs use relatively low amounts of CPU resources. So are the OSD services, so why not combine them? (We use ceph for openstack volume/images storage, 7 shared OSD/KVM nodes, 2 pools, 128 PGs per pool, 2 OSDs per node, 10GigE)

I know that during recovery the OSD memory usage spikes. So I guess that might be one of the reasons. 

But are there any other concrete examples of situations when the hypervisor could compete for CPU/mem resources with the OSD services running on the same node in a way which would noticeably impact the performance of either? 

Kind Regards,
Piotr
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com

[Index of Archives]     [Information on CEPH]     [Linux Filesystem Development]     [Ceph Development]     [Ceph Large]     [Ceph Dev]     [Linux USB Development]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [xfs]


  Powered by Linux