Fix a segfault when tlog encounters platform_error
During destruction, rejoinClusterController actor should be cancelled to avoid accessing TLogData object.
This commit is contained in:
parent
a5d3741e2b
commit
fecffc93e4
|
@ -2548,6 +2548,10 @@ ACTOR Future<Void> rejoinClusterController(TLogData* self,
|
|||
stoppedPromise.send(Void());
|
||||
}
|
||||
|
||||
if (self->terminated.isSet()) {
|
||||
return Void();
|
||||
}
|
||||
|
||||
if (registerWithCC.isReady()) {
|
||||
if (!lastMasterLifetime.isEqual(self->dbInfo->get().masterLifetime)) {
|
||||
// The TLogRejoinRequest is needed to establish communications with a new master, which doesn't have our
|
||||
|
|
Loading…
Reference in New Issue