This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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 2278795 - Possible DB deadlock when publishing a content view with many similar contents
Summary: Possible DB deadlock when publishing a content view with many similar contents
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Views
Version: 6.14.4
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-05-03 05:55 UTC by Hao Chang Yu
Modified: 2024-06-06 17:36 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-06-06 17:36:35 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   SAT-24910 0 None Migrated None 2024-06-06 17:36:34 UTC
Red Hat Knowledge Base (Solution) 7071137 0 None None None 2024-05-21 09:52:24 UTC

Description Hao Chang Yu 2024-05-03 05:55:22 UTC
Description of problem:
This bug had been raised before in bug 2252297 but it was closed because it is hard to reproduce. Thus, I raise a new one for it.

The deadlock error happens when indexing contents of multiple repositories with many similar contents. This could be happened when publishing a content view (in index contents step) with those repositories. For example, RHEL 8 BaseOs and RHEL 8.x BaseOs repos

Steps to reproduce:
1. Create a content view
2. Add RHEL 8 BaseOs repo and multiple many RHEL 8.x BaseOs repositories to the content view.
3. Publish the content view.

Actual results:
ActiveRecord::Deadlocked (PG::TRDeadlockDetected: ERROR:  deadlock detected)
DETAIL:  Process 361390 waits for ShareLock on transaction 85433497; blocked by process 361035.
Process 361035 waits for ShareLock on transaction 85433498; blocked by process 361390.
HINT:  See server log for query details.
CONTEXT:  while inserting index tuple (1530,1) in relation "katello_errata"

Expected results
No Error


Additional info:
The reproducing steps might above might have low chance to reproduce the deadlock error. The higher chance I found is open multiple terminals and run the index errata concurrently.

For example:

Terminal 1:
~~~
Setting[:bulk_load_size] = 250
repo = Katello::ContentView.find(30).versions.last.archived_repos.where("relative_path ilike ?", '%baseos%').sort_by(&:id).first
type = repo.root.repository_type.content_types_to_index.find{|t| t.content_type == 'erratum'}
10.times {Katello::ContentUnitIndexer.new(content_type: type, repository: repo, optimized: false).import_all; sleep 1}
~~~

Terminal 2:
~~~
Setting[:bulk_load_size] = 250
repo = Katello::ContentView.find(30).versions.last.archived_repos.where("relative_path ilike ?", '%baseos%').sort_by(&:id).second
type = repo.root.repository_type.content_types_to_index.find{|t| t.content_type == 'erratum'}
10.times {Katello::ContentUnitIndexer.new(content_type: type, repository: repo, optimized: false).import_all; sleep 1}
~~~

Terminal 3:
~~~
Setting[:bulk_load_size] = 250
repo = Katello::ContentView.find(30).versions.last.archived_repos.where("relative_path ilike ?", '%baseos%').sort_by(&:id).third
type = repo.root.repository_type.content_types_to_index.find{|t| t.content_type == 'erratum'}
10.times {Katello::ContentUnitIndexer.new(content_type: type, repository: repo, optimized: false).import_all; sleep 1}
~~~

Comment 1 Eric Helms 2024-06-06 17:36:35 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.


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