RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1188659 - pcsd status detection is slow
Summary: pcsd status detection is slow
Keywords:
Status: CLOSED DUPLICATE of bug 1207405
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: pcs
Version: 7.1
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Chris Feist
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-02-03 13:45 UTC by Radek Steiger
Modified: 2015-04-20 10:41 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-04-20 10:41:25 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1158491 0 low CLOSED 'pcs cluster status' is documented to be an alias to 'pcs status cluster' but has different output 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 1207405 0 medium CLOSED RFE: please adjust timeouts for pcsd check (or allow to disable them) 2021-10-05 17:55:02 UTC

Internal Links: 1158491 1207405

Description Radek Steiger 2015-02-03 13:45:17 UTC
> Description of problem:

The pcs status output is getting out slowly with a higher number of nodes in the cluster, taking as long as 5 seconds on a 16-node clustere. This is because pcs is checking the states linearly one node after another. We could parallelize this process to make it significantly faster.


> Version-Release number of selected component (if applicable):

pcs-0.9.137-13.el7


> Results:

[root@virt-016 ~]# time pcs status pcsd virt-017
  virt-017: Online
real	0m0.633s
user	0m0.322s
sys	0m0.075s

[root@virt-016 ~]# time pcs status pcsd virt-03{0..5}
  virt-030: Online
  virt-031: Online
  virt-032: Online
  virt-033: Online
  virt-034: Online
  virt-035: Online
real	0m1.778s
user	0m0.345s
sys	0m0.072s

[root@virt-016 ~]# time pcs status pcsd
  virt-016: Online
  virt-017: Online
  virt-018: Online
  virt-023: Online
  virt-024: Online
  virt-027: Online
  virt-028: Online
  virt-029: Online
  virt-030: Online
  virt-031: Online
  virt-032: Online
  virt-033: Online
  virt-034: Online
  virt-035: Online
  virt-036: Online
  virt-037: Online
real	0m6.032s
user	0m0.478s
sys	0m0.084s

Comment 2 Tomas Jelinek 2015-04-20 10:41:25 UTC

*** This bug has been marked as a duplicate of bug 1207405 ***


Note You need to log in before you can comment on or make changes to this bug.