-
Suggestion
-
Resolution: Unresolved
-
None
-
150
-
Hi everyone,
With JCMA 1.7.3, we introduced a new pre-flight check to detect any errors related to data preparation part early on to prevent any migration issue (export errors) during the migration step.
The new pre-flight check prevents customers from pressing the "Run" button till it has produced the results. In older versions of JCMA, this test used to happen after the migration was started. Overall, there is no increase in overall migration time, rather a perceived slowness as you cannot proceed with the migration till you've run these tests.
We understand the concern around more time consumed during the production migration when you've already run multiple tests and might not be anticipating any more issues on the final migration day.
- The team is working on making the export process more efficient, and reducing the overall migration time. You will see an update in the functionality in future releases of JCMA.
- If you need urgent help with any of the migrations you're working on, please reach out to support and they will be able to help you.
Regards,
Radhika Patodiya
Product Manager, Cloud Migrations team
Issue Summary
This is reproducible on Data Center: (yes)
After upgrading to JCMA 1.7.3, the pre-flight checks take noticeably more time to complete than previous versions, eg JCMA 1.7.1, and the user is held up until this completes.
Steps to Reproduce
- Use a JSW project with several thousand issues
- Create a migration plan with the following options
- No Advanced Roadmaps
- All users and groups, preserve group membership
- No Apps
- Click on 'Check for errors' to start the pre-flight checks
Expected Results
The pre-flight checks should complete in a comparable time with 1.7.3, as they do with earlier versions
Actual Results
The 'Data preparation' phase takes a noticeable amount of time to complete
2022-10-06 10:11:46,434+0000 pool-35-thread-14 INFO admin 611x170x1 1gbkk83 172.29.215.229,172.50.0.2 /rest/migration/latest/check/13428e3f83001f5ff14c0d718c4e4e6e53e976e2 [c.a.j.migration.preflight.AsyncCheckExecutor] Pre-flight check for ProjectErrorReport has started. ... 2022-10-06 10:15:25,498+0000 pool-35-thread-14 INFO admin 611x170x1 1gbkk83 172.29.215.229,172.50.0.2 /rest/migration/latest/check/13428e3f83001f5ff14c0d718c4e4e6e53e976e2 [c.a.j.migration.preflight.AsyncCheckExecutor] Pre-flight check for ProjectErrorReport has finished.
This time increases with the number of projects/issues in the plan
2022-10-05 13:25:06,315+0000 pool-35-thread-60 INFO admin 805x6162x1 1cxe875 172.29.209.63,172.50.0.2 /rest/migration/latest/check/plan/4e2ed655-fb1b-41dc-bfb0-28b93cd6c713 [c.a.j.migration.preflight.AsyncCheckExecutor] Pre-flight check for ProjectErrorReport has started. ... 2022-10-05 14:30:47,170+0000 pool-35-thread-60 INFO admin 805x6162x1 1cxe875 172.29.209.63,172.50.0.2 /rest/migration/latest/check/plan/4e2ed655-fb1b-41dc-bfb0-28b93cd6c713 [c.a.j.migration.preflight.AsyncCheckExecutor] Pre-flight check for ProjectErrorReport has finished.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
- is related to
-
- Gathering Interest
- relates to
-
MIG-2033 JCMA Preflights: Migrating filters with JCMA resulted in OOM
-
- Closed
-
-
-
- Closed
-
-
- Gathering Interest
-
- Gathering Interest
-
MOVE-102376 Loading...
-
- causes
-
- mentioned in
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Wiki Page
-
JCMA Preflights: JCMA Pre-flight check for "Data preparation" takes a long time to complete
-
-
Resolution: Unresolved
-
None
-
150
-
Hi everyone,
With JCMA 1.7.3, we introduced a new pre-flight check to detect any errors related to data preparation part early on to prevent any migration issue (export errors) during the migration step.
The new pre-flight check prevents customers from pressing the "Run" button till it has produced the results. In older versions of JCMA, this test used to happen after the migration was started. Overall, there is no increase in overall migration time, rather a perceived slowness as you cannot proceed with the migration till you've run these tests.
We understand the concern around more time consumed during the production migration when you've already run multiple tests and might not be anticipating any more issues on the final migration day.
- The team is working on making the export process more efficient, and reducing the overall migration time. You will see an update in the functionality in future releases of JCMA.
- If you need urgent help with any of the migrations you're working on, please reach out to support and they will be able to help you.
Regards,
Radhika Patodiya
Product Manager, Cloud Migrations team
Issue Summary
This is reproducible on Data Center: (yes)
After upgrading to JCMA 1.7.3, the pre-flight checks take noticeably more time to complete than previous versions, eg JCMA 1.7.1, and the user is held up until this completes.
Steps to Reproduce
- Use a JSW project with several thousand issues
- Create a migration plan with the following options
- No Advanced Roadmaps
- All users and groups, preserve group membership
- No Apps
- Click on 'Check for errors' to start the pre-flight checks
Expected Results
The pre-flight checks should complete in a comparable time with 1.7.3, as they do with earlier versions
Actual Results
The 'Data preparation' phase takes a noticeable amount of time to complete
2022-10-06 10:11:46,434+0000 pool-35-thread-14 INFO admin 611x170x1 1gbkk83 172.29.215.229,172.50.0.2 /rest/migration/latest/check/13428e3f83001f5ff14c0d718c4e4e6e53e976e2 [c.a.j.migration.preflight.AsyncCheckExecutor] Pre-flight check for ProjectErrorReport has started. ... 2022-10-06 10:15:25,498+0000 pool-35-thread-14 INFO admin 611x170x1 1gbkk83 172.29.215.229,172.50.0.2 /rest/migration/latest/check/13428e3f83001f5ff14c0d718c4e4e6e53e976e2 [c.a.j.migration.preflight.AsyncCheckExecutor] Pre-flight check for ProjectErrorReport has finished.
This time increases with the number of projects/issues in the plan
2022-10-05 13:25:06,315+0000 pool-35-thread-60 INFO admin 805x6162x1 1cxe875 172.29.209.63,172.50.0.2 /rest/migration/latest/check/plan/4e2ed655-fb1b-41dc-bfb0-28b93cd6c713 [c.a.j.migration.preflight.AsyncCheckExecutor] Pre-flight check for ProjectErrorReport has started. ... 2022-10-05 14:30:47,170+0000 pool-35-thread-60 INFO admin 805x6162x1 1cxe875 172.29.209.63,172.50.0.2 /rest/migration/latest/check/plan/4e2ed655-fb1b-41dc-bfb0-28b93cd6c713 [c.a.j.migration.preflight.AsyncCheckExecutor] Pre-flight check for ProjectErrorReport has finished.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
- is related to
-
- Gathering Interest
- relates to
-
-
- Closed
-
-
-
- Closed
-
-
- Gathering Interest
-
- Gathering Interest
-
-
- causes
-
- mentioned in
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Wiki Page
-
-
Shraddha Garg
-
- Votes:
-
77 Vote for this issue
- Watchers:
-
77 Start watching this issue
- Created:
- Updated: