I agree but somehow this generates more traffic too. We just need to find a good balance. But I don’t think this will change the scenario where the cluster network is down and OSDs die because of this… –––– Sébastien Han Cloud Engineer "Always give 100%. Unless you're giving blood.” Phone: +33 (0)1 49 70 99 72 Mail: sebastien.han@xxxxxxxxxxxx Address : 10, rue de la Victoire - 75009 Paris Web : www.enovance.com - Twitter : @enovance On 24 Jan 2014, at 11:52, Sylvain Munaut <s.munaut@xxxxxxxxxxxxxxxxxxxx> wrote: > Hi, > >> At some point (if the cluster gets big enough), could this degrade the network performance? Will it make sense to have a separate network for this? >> >> So in addition to public and storage we will have an heartbeat network, so we could pin it to a specific network link. > > I think the whole point of having added hearbeating on public & > cluster network is to be able to detect failure of one network but not > the other. Separating heartbeat on it's own independent network would > be quite counter productive in this respect. > > > Cheers, > > Sylvain
Attachment:
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
