The cluster migration has been finished successfully and it's operational in the new location.
Current slowness issues are solved, eventual changes in the infrastructure will be published in separate status notifications.
In order to achieve proper scalability of main Canary node it will be migrated today.
During the migration such services will be disrupted on Canary:
It will not impact currently configured instances serving content.
We will inform when the migration will be over.
While checking the logs we confirmed that the speed of processing frontend allocation and updates is acceptable.
We are planning to fully stabilize this situation next week, as soon as dedicated Compute Node will be delivered for this service.
We dropped not critical debugging information while processing the Canary cluster, so the processing came back to normal. It's only short-term solution, which will allow us to find time for a better location for the root node of Canary cluster.
We will post here information about eventual changes.
After maintenance on the Canary cluster we learnt that the machine is not performing correctly in the new location.
Currently there are problems with:
There are no problems with serving currently configured frontends.