Description of problem:
Large checkins (e.g. 1350771 ) can result into very long running database transactions. Such long running transactions introduce a danger of lock waits and deadlocks.
Steps to Reproduce:
1. Submit a checkin with large number of hosts and large number of migrated hosts
Checkin creates one big transaction. Migration of guests between hosts require revocation and auto-heal, both are time consuming. I saw a transaction that lasted for 8 hours
Transactions are shorter, at most minutes.
if there is need for this again, we should discuss with katello folks around accepting partial success etc. we should also focus on one transaction per hypervisor imo.