Migrate a Queue Between Pools
In order to support manual rebalancing (QoS) of a large deployment, there should be a means to migrate a queue from one pool to another. Ideally, a solution to this problem will result in zero to minimal downtime, and if downtime is necessary, it only affects the owner of that particular queue.
Also to consider is migrating a queue as quickly as possible. It can't take days.
Blueprint information
- Status:
- Not started
- Approver:
- Kurt Griffiths
- Priority:
- Low
- Drafter:
- Allele Dev
- Direction:
- Needs approval
- Assignee:
- Flavio Percoco
- Definition:
- Discussion
- Series goal:
- Accepted for kilo
- Implementation:
-
Not started
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Deprioritized for Juno, since we have other things such as v1.1 and graduation that will likely take all our time. (kgriffs)
Noisy neighbor can be addressed by being able to migrate/rebalance shards to progressively less-crowded pools. You can take this to an extreme by isolating someone in their own micro storage cluster using docker. You would want to also be able to handle a queue that is really busy for a while and then "cools down" for a while.
Noisy neighbor doesn't really apply to the web heads because we can just round-robin and autoscale the load
--
Moving to Kilo. I don't believe this will make it into Juno
-- flaper87 2014-08-04
Work Items
Dependency tree
* Blueprints in grey have been implemented.
