Skip to content

IoTConsensusV2: Support SyncLag And Buffer Control For Deletion #14026

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
OneSizeFitsQuorum merged 1 commit into from
Nov 8, 2024
Merged

IoTConsensusV2: Support SyncLag And Buffer Control For Deletion #14026

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions ...rg/apache/iotdb/db/pipe/connector/protocol/pipeconsensus/PipeConsensusAsyncConnector.java
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -406,7 +406,16 @@ public void transfer(Event event) throws Exception {

// Transfer deletion
if (event instanceof PipeDeleteDataNodeEvent) {
PipeDeleteDataNodeEvent deleteDataNodeEvent = (PipeDeleteDataNodeEvent) event;
boolean enqueueResult = addEvent2Buffer(deleteDataNodeEvent);
if (!enqueueResult) {
throw new PipeRuntimeConnectorRetryTimesConfigurableException(
ENQUEUE_EXCEPTION_MSG, Integer.MAX_VALUE);
}
retryConnector.transfer(event);
// Since transfer method will throw an exception if transfer failed, removeEventFromBuffer
// will not be executed when transfer failed.
this.removeEventFromBuffer(deleteDataNodeEvent);
return;
}

Expand Down