Azure Compute Service worker becomes “busy” following scale-up
问题 I'm running one service in Azure with 4 worker instances. When I scale up to 5 worker instances the first instance that had started goes into the "busy" state. Why is that? What happens during scale up? Does azure re-run all the startup tasks? I'm very confused and can't seem to find any documentation on this. After scaling up to 5 instances the first instance changes its status to: Busy (Waiting for role to start... Application startup tasks are running. [2014-08-12T18:36:52Z]) And the java