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 1539784 - [RFE] Improve creation time for sosreport by using multiple cores on archiving process
Summary: [RFE] Improve creation time for sosreport by using multiple cores on archivin...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: sos
Version: 7.4
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: rc
: ---
Assignee: Pavel Moravec
QA Contact: Miroslav Hradílek
URL:
Whiteboard:
Depends On: 1545357
Blocks: 1477664 1552138
TreeView+ depends on / blocked
 
Reported: 2018-01-29 15:36 UTC by Steffen Froemer
Modified: 2021-09-09 13:06 UTC (History)
8 users (show)

Fixed In Version: sos-3.6-1.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-10-30 10:31:19 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github sosreport sos pull 1196 0 None None None 2018-03-03 14:17:06 UTC
Red Hat Product Errata RHEA-2018:3144 0 None None None 2018-10-30 10:33:21 UTC

Description Steffen Froemer 2018-01-29 15:36:46 UTC
1. Proposed title of this feature request
Improve runtime for sosreport by adding the usage of threads to archiving method


3. What is the nature and description of the request?
The time for creating sosreport on systems with high amount of logs resulting in large archives, can be tuned by adding thread-support easily.


4. Why does the customer need this? (List the business requirements here)
On debugging issues in RHV environment, the sosreport will require to archive a lot of logs which in sum have a large amount of size. Archiving these items will need a lot of time, because sos is only using single-thread for creating the archive

5. How would the customer like to achieve this? (List the functional requirements here)
Using more processors for the archiving process


6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
Collect a sosreport without the tuning enabled and measure the time. With tuning enabled, the creation of sosreport would require less time.


7. Is there already an existing RFE upstream or in Red Hat Bugzilla?
https://github.com/sosreport/sos/issues/1196


8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?
asap


9. Is the sales team involved in this request and do they have any additional input?
no


10. List any affected packages or components.
sos


11. Would the customer be able to assist in testing this functionality if implemented?
yes

Comment 4 Pavel Moravec 2018-01-29 15:43:07 UTC
Feature makes sense (maybe bit simplified the includes from the upstream PR). Due to the phase of 7.5, rescheduling to 7.6

Comment 5 Pavel Moravec 2018-04-17 07:14:34 UTC
This relies on sos upstream:

https://github.com/sosreport/sos/pull/1199

that depends on python-futures package, that is not in RHEL repo/channels.

Cond nack until the package is there (request for that in process).

Comment 6 Pavel Moravec 2018-04-17 10:18:16 UTC
(In reply to Pavel Moravec from comment #5)
> This relies on sos upstream:
> 
> https://github.com/sosreport/sos/pull/1199
> 
> that depends on python-futures package, that is not in RHEL repo/channels.
> 
> Cond nack until the package is there (request for that in process).

There is already BZ for that, 1545357 , so devel_ack+ for 7.6.

(how one can remove devel cond nak? I can only change the type but can't reset it to None)

Comment 9 Pavel Moravec 2018-06-22 16:13:44 UTC
PR POSTed to upstream few days ago.

Comment 13 errata-xmlrpc 2018-10-30 10:31:19 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2018:3144


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