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 976861 - Possible parallel communication problem with 11+ nodes cluster
Summary: Possible parallel communication problem with 11+ nodes cluster
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: luci
Version: 6.4
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: rc
: ---
Assignee: Ryan McCabe
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-06-21 17:02 UTC by Jan Pokorný [poki]
Modified: 2023-09-14 01:46 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-11-07 21:40:39 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Jan Pokorný [poki] 2013-06-21 17:02:09 UTC 
Just noticed that send_batch_parallel function cannot currently cope with
11+ target nodes (provided with only send a single message during
the cluster communication round).

First 10 items of communication batch are send OK, but than the limit
of threads kicks in and the rest of items is silently ignored.

If my (and jrummy's) observation is correct, the algorithm needs to be
slightly extended to be robust enough (coping with at least 16 nodes
as supported is the very entry level fix here, universal one is better).
Comment 3 Jan Pokorný [poki] 2013-06-26 19:03:19 UTC 
Ok, attachment 765707 [details] (of [bug 978479]) seems to prove [*] that no
end-point of the "multicast" is ever ignored regardless the threads limit.
The rest will simplt be proceeded in one of subsequent rounds until
the queue is empty.

Lowering the priority, but keeping this opened until final statement
is made.

[*] During that experiment, limit of threads was hardcoded as 3, however
the communication happened across 6 (later 8 nodes).  What can be observed
that the communication was split into several subsequent
rounds of 3 communication end-points at a time.
Comment 11 Chris Feist 2017-11-07 21:40:39 UTC 
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/
Comment 12 Red Hat Bugzilla 2023-09-14 01:46:56 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days
Note You need to log in before you can comment on or make changes to this bug.