osdir.com


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

Re: Openstack and Cassandra


Thanks for the info Romain, 

Can you tell me please what are the implications of not using CPU Pinning?



 
Shalom Sagges
DBA
T: +972-74-700-4035
We Create Meaningful Connections
 

On Wed, Dec 28, 2016 at 7:01 PM, Romain Hardouin <romainh_ml@xxxxxxxx> wrote:
Kilo is a bit old but the good news is that CPU pinning is available which IMHO is a must to run C* on Production.
Of course your bottleneck will be shared HDDs.

Best,

Romain


Le Mardi 27 décembre 2016 10h21, Shalom Sagges <shaloms@xxxxxxxxxxxxxx> a écrit :


Hi Romain, 

Thanks for the input!

We currently use the Kilo release of Openstack. Are you aware of any known bugs/issues with this release?
We definitely defined anti-affinity rules regarding spreading C* on different hosts. (I surely don't want to be woken up at night due to a failed host ;-) )

Regarding Trove, I doubt we'll use it in Production any time soon.

Thanks again!




 
Shalom Sagges
DBA
T: +972-74-700-4035
We Create Meaningful Connections
 

On Mon, Dec 26, 2016 at 7:37 PM, Romain Hardouin <romainh_ml@xxxxxxxx> wrote:
Hi Shalom,

I assume you'll use KVM virtualization so pay attention to your stack at every level:
- Nova e.g. CPU pinning, NUMA awareness if relevant, etc. Have a look to extra specs.
- libvirt 
- KVM
- QEMU

You can also be interested by resources quota on other OpenStack VMs that will be colocated with C* VMs.
Don't forget to define anti-affinity rules in order to spread out your C* VMs on different hosts.
Finally, watch out versions of libvirt/KVM/QEMU. Some optimizations/bugs are good to know.

Out of curiosity, which OpenStack release are you using?
You can be interested by Trove but C* support is for testing only.

Best,

Romain






This message may contain confidential and/or privileged information. 
If you are not the addressee or authorized to receive this on behalf of the addressee you must not use, copy, disclose or take action based on this message or any information herein. 
If you have received this message in error, please advise the sender immediately by reply email and delete this message. Thank you.




This message may contain confidential and/or privileged information. 
If you are not the addressee or authorized to receive this on behalf of the addressee you must not use, copy, disclose or take action based on this message or any information herein. 
If you have received this message in error, please advise the sender immediately by reply email and delete this message. Thank you.