-
Type:
Suggestion
-
Resolution: Unresolved
-
Component/s: Jira - Migration Assistant - Export
-
None
Issue Summary
There has been a recent HOT, where we found out that the migration_request_catalogue table which is used for consistency checks was very large 400+gb.
Link of hot discussion thread : https://atlassian.slack.com/archives/C0BJACUUUET/p1784672578123329
Question : Since now we are 100% V4, Have we already turned shadow-mode capability off for incoming migrators altogether (so that no, further large tables come from migration)
Steps to Reproduce
- Turn on shadow migrations FF and migrate
Expected Results
Actual Results
The below exception is thrown in the xxxxxxx.log file:
...
Workaround
Required, if there is no workaround please state:
Currently there is no known workaround for this behavior. A workaround will be added here when available