mirror of https://github.com/apache/cloudstack.git
748603f62d
we use 'update count' to make sure agent status transformation is atomic. However, atomic means success or fail which is not true for agent status. some important transformation occassionally fails because race condition that some other one is changing it simultaneously which finally makes agent stuck in a wrong status. use reenterent lock to serialize the agent status transformation. this memory lock works in clusterd environement as well because in our design an agent is only active in one mgmt server status 13269: resolved fixed |
||
|---|---|---|
| .. | ||
| conf | ||
| scripts | ||
| src/com/cloud | ||
| test | ||
| .classpath | ||
| .project | ||