Concurrency bug for multiple deployments within same second
Bug #1462130 reported by
Melissa Kam
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Solum |
Triaged
|
High
|
Devdatta Kulkarni | ||
Bug Description
Multiple deployments of the same app within the same second causes multiple servers to remain instead of only keeping one and deleting the others.
The deployer uses the created_at time to determine which assembly needs to be deleted. If an app is deployed within the same second, though, the created_at time is the same, so none of the assemblies are deleted.
| description: | updated |
| Changed in solum: | |
| importance: | Undecided → High |
| milestone: | none → 2015.1.1 |
| status: | New → Triaged |
| Changed in solum: | |
| assignee: | nobody → Devdatta (devdatta-kulkarni) |
Revision history for this message
| James Li (james-li-3) wrote | #1 |
| tags: | added: solum-deployer |
To post a comment you must log in.
A potential fix would be not to use the timestamp from mysql, but to generate a timestamp with enough resolution (say microsecond) in solum api code. That is to say we actually need the time when a deployment request enters solum system, rather than the time when it is stored into DB.