Page MenuHomePhabricator

When allocating services, the cluster should choose the same dbx and repox nodes
Closed, ResolvedPublic

Description

Currently, when a new instance is allocated it randomly chooses one open AlmanacClusterDatabaseServiceType service and one open AlmanacClusterRepositoryServiceType service.

In the general case, this means that an instance could end up on dbx002 but on repox009. This is technically OK, but it's nice for now to have all the dbx004 instances be on repox004 since this is conceptually easier to reason about and react to if manual intervention is required to respond to an operational issue.

Implementing this would let us have multiple service tiers open simultaneously without losing the convenience of node correspondence.

Revisions and Commits

Restricted Differential Revision

Event Timeline

epriestley raised the priority of this task from to Low.
epriestley updated the task description. (Show Details)
epriestley added a project: Phacility.
epriestley moved this task to Do After Launch on the Phacility board.
epriestley added a subscriber: epriestley.
epriestley renamed this task from When allocating services, the cluster should choose the same dbx and repox node to When allocating services, the cluster should choose the same dbx and repox nodes.Aug 31 2015, 1:35 PM
epriestley added a revision: Restricted Differential Revision.Nov 21 2015, 8:12 PM
epriestley closed this task as Resolved by committing Restricted Diffusion Commit.Nov 21 2015, 8:25 PM
epriestley added a commit: Restricted Diffusion Commit.