Forwarded to devs Migration of 1 domain's single step takes over an hour

[tkalfaoglu]

Username: tkalfaoglu

TITLE

Migration of 1 domain's single step takes over an hour

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

Centos 8 Obsidian

PROBLEM DESCRIPTION

Moving 326 domains from one server to another on the same data center. Both server's loads are almost none.
Moving one domain currently for testing..

However, it has been 1 hour at THIS step of the migration:

Jul 7 14:19:32 ocean systemd[1]: Started Plesk task: Event 'maillist_update' for object with ID '6' (task=7900 process=7900 trace=20860:60e58da9737f6).
Jul 7 14:19:32 ocean systemd[1]: run-plesk-task-7900.service: Succeeded.
Jul 7 14:19:32 ocean systemd[1]: Stopped Plesk task: Event 'maillist_update' for object with ID '6' (task=7900 process=7900 trace=20860:60e58da9737f6).
Jul 7 14:19:32 ocean systemd[1]: Started Plesk task: Event 'maillist_update' for object with ID '6' (task=7901 process=7901 trace=20860:60e58da9737f6).
Jul 7 14:19:32 ocean systemd[1]: run-plesk-task-7901.service: Succeeded.
Jul 7 14:19:32 ocean systemd[1]: Stopped Plesk task: Event 'maillist_update' for object with ID '6' (task=7901 process=7901 trace=20860:60e58da9737f6).
Jul 7 14:19:33 ocean systemd[1]: Started Plesk task: Event 'maillist_update' for object with ID '6' (task=7902 process=7902 trace=34567:60e58dc452a70).
Jul 7 14:19:33 ocean systemd[1]: run-plesk-task-7902.service: Succeeded.
Jul 7 14:19:33 ocean systemd[1]: Stopped Plesk task: Event 'maillist_update' for object with ID '6' (task=7902 process=7902 trace=34567:60e58dc452a70).
Jul 7 14:19:33 ocean systemd[1]: Started Plesk task: Event 'maillist_update' for object with ID '6' (task=7903 process=7903 trace=34567:60e58dc452a70).

I understand that speeding up the entire migration tool is difficult, BUT at least this step, meaning,

START: Restore hosting settings of subscription

step needs to be speeded up by a factor of 10.

STEPS TO REPRODUCE

Simply start any migration from obsidian to obsidian.

ACTUAL RESULT

Hours wasted.

EXPECTED RESULT

Results within the same day

ANY ADDITIONAL INFORMATION



YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Help with sorting out

 

[tkalfaoglu]

NOTE: I believe this is is due to the way PLESK migrates mailing lists. ONE subscriber at a time. So each subscriber takes a few seconds.. Multiply that with ten thousand, and you wait for 5 hours or more.

 

[IgorG]

We've tested on our internal infrastructure (quite slow VM with 1GB memory) and got around 1 minute for 100 mail list recipients, less than 1 second per subscriber. It would take about 2 hours for 10 000 mail list recipients. Developers think that's ok to wait for 2 hours to migrate configuration like that, and they don't see any real problem here. Of course, performance could be improved, but that does not look like a common configuration.

I'd suggest you create a request at UserVoice.

 

[tkalfaoglu]

Thank you -the server I manage has about a dozen lists with 10-20 thousand subscribers. Hence the days required to migrate them.

 

[tkalfaoglu]

Another interesting thing: Since it takes many hours, the migration tool times out and marks the domains with large lists with a red (!) mark as failed.