Hi Miroslav, Thank you for your helpful suggestions! I followed your advice and used the pcs command with the -f option to create the cluster CIB configuration, and then pushed it using pcs cluster cib-push. I'm happy to report that the configuration time has been significantly reduced! The resource configuration time has been reduced from the original 2 hours and 31 minutes to just 31 minutes. I appreciate your help in pointing me in the right direction. Thanks again for your assistance! Best regards, Zufei Chen
attachment: new create bash: pcs_create.sh ------------------------------------------------------------------------------------------------------------------- Message: 1 Date: Thu, 24 Oct 2024 14:01:57 +0200 From: Miroslav Lisik <mli...@redhat.com> To: users@clusterlabs.org Subject: Re: [ClusterLabs] poor performance for large resource configuration Message-ID: <a9841659-0249-47b6-982c-132880d50...@redhat.com> Content-Type: text/plain; charset=UTF-8; format=flowed On 10/21/24 13:07, zufei chen wrote: > Hi all, > > background? > > 1. lustre(2.15.5) + corosync(3.1.5) + pacemaker(2.1.0-8.el8) + > pcs(0.10.8) > 2. there are 11 nodes in total, divided into 3 groups. If a node > fails within a group, the resources can only be taken over by > nodes within that group. > 3. Each node has 2 MDTs and 16 OSTs. > > Issues: > > 1. The resource configuration time progressively increases. the > second mdt-0? cost only???8s?the last?ost-175 cost??1min:37s > 2. The total time taken for the configuration is approximately 2 > hours and 31 minutes. Is there a way to improve it? > > > attachment: > create bash: pcs_create.sh > create log:?pcs_create.log > > _______________________________________________ > Manage your subscription: > https://lists.clusterlabs.org/mailman/listinfo/users > > ClusterLabs home: https://www.clusterlabs.org/ Hi, you could try to create cluster CIB configuration with pcs commands on a file using the '-f' option and then push it to the pacemaker all at once. pcs cluster cib > original.xml cp original.xml new.xml pcs -f new.xml <command> ... ... pcs cluster cib-push new.xml diff-against=original.xml And then wait for the cluster to settle into stable state: crm_resource --wait Or there is pcs command since version v0.11.8: pcs status wait [<timeout>] I hope this will help you to improve the performance. Regards, Miroslav ------------------------------ Subject: Digest Footer _______________________________________________ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/ ------------------------------ End of Users Digest, Vol 117, Issue 24 **************************************
pcs_create.sh
Description: Binary data
_______________________________________________ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
