cinder nfs backup performance

asked 2017-05-12 04:12:57 -0600

Mario Sommer gravatar image


Does anyone actually use cinder backup to NFS in production?

In my test system (6 Core XeonE5-2603 @ 1.70GHz) even a single small backup job (10GB volume) creates so much CPU load, that the cinder-backup service fails to send its status to RabbitMQ in time. Setting the cinder-backup service "down" and prohibiting a second backup job to be started .

2017-05-12 10:38:41.541 18978 WARNING oslo.service.loopingcall [req-d1110b12-7e8f-4eea-9ee0-fafb27614906 Openstack Admin 15d30213519a4e55aa38821b1dc9f21c - - -] Function 'cinder.service.Service.report_state' run outlasted interval by 118.31 sec

Are there any recommendations for tuning the cinder backup service?

edit retag flag offensive close merge delete