From f27f816fbc0dd236546194398a2f8d2d82ca3b43 Mon Sep 17 00:00:00 2001 From: SS Date: Wed, 8 Dec 2021 20:21:29 +0800 Subject: [PATCH] [skip ci] Fix grammar (#12997) Signed-off-by: sida shen --- docs/design_docs/datanode_recovery_design_0513_2021.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/design_docs/datanode_recovery_design_0513_2021.md b/docs/design_docs/datanode_recovery_design_0513_2021.md index 3b0af0b39e..78e39617dd 100644 --- a/docs/design_docs/datanode_recovery_design_0513_2021.md +++ b/docs/design_docs/datanode_recovery_design_0513_2021.md @@ -40,8 +40,8 @@ After DataNode subscribes to a stateful vchannel, DataNode starts to work, or mo Vchannel is stateful because we don't want to process twice what's already processed, as a "processed" message means its already persistent. In DataNode's terminology, a message is processed if it's been flushed. -DataCoord tells DataNode stateful vchannel info through RPC `WatchDmChannels`, so that DataNode won't process -the same messages over and over again. So flowgraph needs ability to consume messages in the middle of a vchannel. +DataCoord tells DataNode stateful vchannel info through RPC `WatchDmChannels` so that DataNode won't process +the same messages over and over again. So flowgraph needs the ability to consume messages in the middle of a vchannel. DataNode tells DataCoord vchannel states after each flush through RPC `SaveBinlogPaths`, so that DataCoord keeps the vchannel states update.