This repository has been archived by the owner on Jan 9, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 24
The errata migration continues to fail with "pymongo.errors.DocumentTooLarge: BSON document too large" error #572
Labels
Comments
hao-yu
added a commit
to hao-yu/pulp-2to3-migration
that referenced
this issue
Jul 19, 2022
hao-yu
added a commit
to hao-yu/pulp-2to3-migration
that referenced
this issue
Jul 26, 2022
hao-yu
added a commit
to hao-yu/pulp-2to3-migration
that referenced
this issue
Jul 26, 2022
When pre-migrating errata, make query in batch to prevent the BSON too large error. closes pulp#572
ggainey
pushed a commit
that referenced
this issue
Aug 4, 2022
When pre-migrating errata, make query in batch to prevent the BSON too large error. closes #572
ggainey
pushed a commit
to ggainey/pulp-2to3-migration
that referenced
this issue
Aug 5, 2022
When pre-migrating errata, make query in batch to prevent the BSON too large error. closes pulp#572
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=2074099
Version
satellite-6.9.9-1.el7sat.noarch
tfm-rubygem-katello-3.18.1.53-1.el7sat.noarch
tfm-rubygem-pulp_2to3_migration_client-0.10.0-1.el7sat.noarch
Describe the bug
Description of problem:
The following error was supposed to be fixed via Bugzilla https://bugzilla.redhat.com/show_bug.cgi?id=2003888 but it still exists after upgrade to 6.9.8 when the count of ERRATA's are way to be migrated is very high.
This happens even if we configure the value of PULP_CONTENT_PREMIGRATION_BATCH_SIZE as low as 25 and repeatedly try.
Version-Release number of selected component (if applicable):
Satellite 6.9.8
How reproducible:
At times when ERRATA count is very high (assuming)
Steps to Reproduce:
Same as Bugzilla https://bugzilla.redhat.com/show_bug.cgi?id=2003888.
Perhaps, sync a good amount of repo to have a huge amount of errata to be migrated during pulp 2 - pulp3 content migration and then attempt the same on a Satellite 6.9.8
Actual results:
Expected results:
The satellite should be able properly to use the PULP_CONTENT_PREMIGRATION_BATCH_SIZE value and should be able to handle a large amount of ERRATA migration as well without any such errors.
Additional info:
I think it is because the query size is too large when using "id__in=". Based on what I observed from the below tests, Pymongo will send full query to server once and then follow by the "GetMore" operation. Regardless of what batch_size we set or what fields we are limiting, they don't affect the query size. That means if we query half a million of ids in 1 shot, we will (should) get the BSON limit error.
I am using RPM for testing because it always has more records than errata. Although, I still don't understand why the migration kept or only failed when migrating errata.
The text was updated successfully, but these errors were encountered: