Skip to content

Force a new history uuid when force allocating a stale primary #26712

Closed
Closed
Force a new history uuid when force allocating a stale primary#26712
Assignees
bleskesdnhatn
Labels
:Distributed/DistributedA catch all label for anything in the Distributed Area. Please avoid if you can.>enhancement
@bleskes

Description

@bleskes
bleskes
opened on Sep 19, 2017

This is a follow up to #26694 which didn't cover that edge case. The rationale is similar - it's unsafe to do ops based recoveries from those primaries

Metadata

Metadata

Assignees

Labels

:Distributed/DistributedA catch all label for anything in the Distributed Area. Please avoid if you can.>enhancement

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions