On 7/6/2018 9:33 AM, Alan Bishop wrote:

On Fri, Jul 6, 2018 at 10:18 AM Amy Marrich <[email protected] <mailto:[email protected]>> wrote:

    Hey,

    Forwarding to the Dev list as you may get a better response from
    there.

    Thanks,

    Amy (spotz)

    On Thu, Jul 5, 2018 at 11:30 PM, Keynes Lee/WHQ/Wistron
    <[email protected] <mailto:[email protected]>> wrote:

        Hi

        When making “cinder backup-create”

        We found the process “cinder-backup” use 100% util of 1 CPU
        core on an OpenStack Controller node.

        It not just causes a bad backup performance, also make the
        openstack-cinder-backup unstable.

        Especially when we make several backup at the same time.

        The Controller Node has 40 CPU cores.

        Can we assign more CPU resources to cinder-backup ?


This has been addressed in [1], but it may not be in the release you're using.

[1] https://github.com/openstack/cinder/commit/373b52404151d80e83004a37d543f825846edea1


In addition to the change above we also have https://review.openstack.org/#/c/537003/ which should also help with the stability issues.  That has been backported as far as Pike.

The change for multiple processes is only in master for the Rocky release right now.

Jay

Alan

        cid:[email protected]

                

        *Keynes  Lee **李****俊****賢*

        Direct:

                

        +886-2-6612-1025

        Mobile:

                

        +886-9-1882-3787

        Fax:

                

        +886-2-6612-1991

                

        E-Mail:

                

        [email protected] <mailto:[email protected]>

        
*---------------------------------------------------------------------------------------------------------------------------------------------------------------*

        *This email contains confidential or legally privileged
        information and is for the sole use of its intended recipient. *

        *Any unauthorized review, use, copying or distribution of this
        email or the content of this email is strictly prohibited.*

        *If you are not the intended recipient, you may reply to the
        sender and should delete this e-mail immediately.*

        
*---------------------------------------------------------------------------------------------------------------------------------------------------------------*


        _______________________________________________
        Community mailing list
        [email protected]
        <mailto:[email protected]>
        http://lists.openstack.org/cgi-bin/mailman/listinfo/community


    __________________________________________________________________________
    OpenStack Development Mailing List (not for usage questions)
    Unsubscribe:
    [email protected]?subject:unsubscribe
    <http://[email protected]?subject:unsubscribe>
    http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to