weizhouapache commented on PR #9201:
URL: https://github.com/apache/cloudstack/pull/9201#issuecomment-2168182709

   > @vishesh92 I had a look of the process of vm deployment, would it make 
sense to lock the method below ?
   > 
   > 
https://github.com/apache/cloudstack/blob/cb9b3134f7fff972b63d8565a4d021f8ea918903/server/src/main/java/com/cloud/deploy/DeploymentPlanningManagerImpl.java#L303-L304
   > 
   > rename it to `planDeploymentInternal` and create a new `planDeployment` 
using Transaction ?
   
   I am also wondering what processes should be locked, maybe until the host is 
determined ?
   
   maybe we could introduce some mechanism, for example
   - when create a vm , lock the `network` table (for example, to fix #7907 , 
cc @abh1sar ) and `resource_limit` table (to fix the resource issue ?)
   - when start a vm, lock the `affinity_group` table and some other tables if 
needed ?
   
   the problem is, it could lead to high latency if the platform is large.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to