-
Notifications
You must be signed in to change notification settings - Fork 4
Closed
Labels
scope:data-migratorChanges to the Data Migrator.Changes to the Data Migrator.version:migration 0.3.0version:migration 0.3.0-alpha3
Description
Environment (Required on creation)
Data Migrato 0.3-SNAPSHOT
Description (Required on creation; please attach any relevant screenshots, stacktraces, log files, etc. to the ticket)
In Data Migrator History, the same entities are retried multiple times when --retry-skipped is passed.
Steps to reproduce (Required on creation)
- Have entities that are permanently skipped even after retrying multiple times.
- Migrate entities
- Retry entity migration with
--history --retry-skippedflag. - Look at log output.
Observed Behavior (Required on creation)
The log output shows that entities are retried multiple times in the same run.
Expected behavior (Required on creation)
Logs show that entities are retried only once within the same retry run.
Root Cause (Required on prioritization)
This code expects that there are no entities that are permanently skipped, but they actually exist:
https://github.com/camunda/camunda-7-to-8-migration-tooling/blame/2708edae9f2c60edbf69d95478d05b25d6896eb5/data-migrator/core/src/main/java/io/camunda/migration/data/impl/clients/DbClient.java#L171-L177
Examples: inconsistencies, CMMN-related user tasks, and standalone user tasks.
Solution Ideas
Keep track of which entities have been retried already and don't retry them again.
Workarounds
Hints
Links
Breakdown
Pull Requests
Dev2QA handover
- Does this ticket need a QA test, and the testing goals are not clear from the description? Add a Dev2QA handover comment
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
scope:data-migratorChanges to the Data Migrator.Changes to the Data Migrator.version:migration 0.3.0version:migration 0.3.0-alpha3
Type
Fields
Give feedbackNo fields configured for Bug.