I think you may also consider risk like kernel crashes etc,since storage and
compute node are sharing the same box.
Date: Wed, 12 Nov 2014 14:51:47 +
From: pieter.koo...@me.com
To: ceph-users@lists.ceph.com
Subject: Re: [ceph-users] Ceph and Compute on same hardware?
Hi,
Thanks for the
> A while back on a blog I saw mentioned that Ceph should not be run on compute
> nodes and in the general
> sense should be on dedicated hardware. Does this really still apply?
In my opinion storage needs to be rock-solid.
Running other (complex) software on a Ceph node increases the chances of
Hi,
Thanks for the replies. Likely will not choose this method but wanted to
make sure that it was a good technical reason rather than just a "best
practice". I did not quite think of "conntracker" at the time so this is a
good one to consider.
Thanks
Pieter
On 12 November 2014 14:30, Haomai Wa
On Wed, Nov 12, 2014 at 5:30 PM, Haomai Wang wrote:
> Actually, our production cluster(up to ten) all are that ceph-osd ran
> on compute-node(KVM).
>
> The primary action is that you need to constrain the cpu and memory.
> For example, you can alloc a ceph cpu-set and memory group, let
> ceph-osd
Actually, our production cluster(up to ten) all are that ceph-osd ran
on compute-node(KVM).
The primary action is that you need to constrain the cpu and memory.
For example, you can alloc a ceph cpu-set and memory group, let
ceph-osd run with it within limited cores and memory.
The another risk i
Technically there's no reason it shouldn't work, but it does complicate
things. Probably the biggest worry would be that if something bad
happens on the compute side (say it goes nuts with network or memory
transfers) it could slow things down enough that OSDs start failing
heartbeat checks ca
