Re:Inside the longest Atlassian outage
by anarazel on Wednesday April 13, 2022 @09:20PM
(#31022361)
ISTM the fairly obvious approach would be to bring up a complete copy of the affected database(s) and move the affected tenants to that "copy", while eventually deleting non-affected tenants. Can't imagine they don't have the ability to move tenants to different shards, they got to need that to deal with quickly growing customers etc.
[ Parent
| on HN ]
There are no comments on this comment yet.