server_id not truly unique
Bug #1365614 reported by
Morgan Jones
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack DBaaS (Trove) |
Triaged
|
Low
|
Morgan Jones |
Bug Description
During instance creation, a "unique" server_id is generated for each trove instance. The server_id is derived from the instance id modulo 65535, which of course is not truly unique. This has not been an issue to date, but the replication feature relies on the server_ids being unique. Eventually, a non-unique server_id will be generated within a master/slave set and replication will fail.
We need to come up with a better way of assigning server_ids.
See trove/common/
Changed in trove: | |
status: | New → Triaged |
importance: | Undecided → Low |
Changed in trove: | |
milestone: | none → juno-rc1 |
Changed in trove: | |
assignee: | nobody → Morgan Jones (6-morgan) |
Changed in trove: | |
milestone: | kilo-1 → next |
milestone: | next → kilo-2 |
Changed in trove: | |
milestone: | kilo-2 → kilo-3 |
Changed in trove: | |
milestone: | kilo-3 → ongoing |
To post a comment you must log in.
Why is the importance of this "Low"?
Morgan, what are the consequences of not having a unique server id?