Refactor subnet object in df db
Bug #1549125 reported by
Li Ma
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| DragonFlow |
Fix Released
|
High
|
Unassigned | ||
Bug Description
The reason why this inconsistency problem is discovered is that the DF DB doesn't have a dedicated table for subnet. When updating subnet, it updates the corresponding network table 'lswitch', which increases the frequency of concurrent read/write operations on the same key. In order to reduce the possibility of race condition, we need to refactor the db schema.
| Changed in dragonflow: | |
| importance: | Undecided → Wishlist |
| assignee: | nobody → Li Ma (nick-ma-z) |
| importance: | Wishlist → Low |
Revision history for this message
| Omer Anson (omer-anson) wrote | #1 |
| Changed in dragonflow: | |
| importance: | Low → High |
| Changed in dragonflow: | |
| assignee: | Li Ma (nick-ma-z) → nobody |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to dragonflow (master) | #2 |
| Changed in dragonflow: | |
| status: | New → Fix Released |
To post a comment you must log in.
This may be needed for Selective-Proactive