Bug 971476 - Fix DB lock up issue that occurs when simultaneously registering systems and unregistering systems from a single ORG
Fix DB lock up issue that occurs when simultaneously registering systems and ...
Status: CLOSED EOL
Product: Red Hat Network
Classification: Red Hat
Component: RHN/Backend (Show other bugs)
MR50 (AMS)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Nicky
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-06-06 11:45 EDT by Brooks
Modified: 2017-07-05 11:17 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-07-05 11:17:51 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Brooks 2013-06-06 11:45:17 EDT
Description of problem:

From PRB0000187,
"
RHN database has been encountering with blocking locks due to activity against the redhat specific org id (org_id 711497). speicifically the login qa@redhat.com.
This org has thousands of servers and any subscibe or delete server activity against the org is causing lot of row lock contention against rows in RHNPRIVATECHANNELFAMILY table specific to the org.
AMS and DBA team has been able to reproduce the issue in stage environment and the following link has info regarding the test and the highlevel root cause

We have been noticing the locks any time of the day but recently we have noticed this mainly between 2 and 7 AM EDT.
"

Version-Release number of selected component (if applicable):
N/A

How reproducible:
Every time in Production

SETUP for reproduction steps:
1. Must have several systems that are already registered to RHN that should be prepared to un-register from the RHN SSM(system set manager) in 
2. Must have several systems that are not registered to RHN that are prepared to register to RHN
3. Must register and unregister systems within the same ORG example user. qa@redhat.com


Steps to Reproduce:
(Run Steps 1 and 2 simultaneously, first open terminal on the different systems that are mentioned in the 'Setup' procedures)
1. Within SSM (system set manager) in the RHN UI, unregister multiple systems at the same time within the same Org your registering systems in Step 2.

2. Within the first system that is prepared to be registered to RHN, run the following command in terminal(of course, using the appropriate credentials) :

rhnreg_ks --username={Username} --password={Password}



Actual results:
The delete update within the RHN DB happens when 20 systems are deleted from the same Org

Expected results:
The delete update within the the RHN DB immediately happens when 1 system is deleted.

Additional info:

This bug was created in response to the issue reported on PRB0000187
Comment 1 Brooks 2013-06-06 11:47:41 EDT
US34936 added to AMS Backlog
Comment 2 Thomas "Shea" DeAntonio 2017-07-05 11:17:51 EDT
As you may already be aware, Red Hat is transitioning from the Red Hat Network (RHN) hosted interface to the Red Hat Subscription Management (RHSM) interface in July 2017. Red Hat has invested in and seen success from RHN for many years, and used that experience to build more robust technologies like RHSM. 
 
If you have not yet migrated your RHN systems to RHSM or you are a Red Hat Satellite customer, please review the information from. https://access.redhat.com/products/red-hat-subscription-management#migration. 
 
Since we are shutting down RHN, no further actions will be taken with this bug or enhancement request.  You can find additional information at RHSM product page (https://access.redhat.com/products/red-hat-subscription-management).  If you have further questions, please contact support (https://access.redhat.com/products/red-hat-subscription-management#support).

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