From 59104d7e0878fc82d309fb233f5c48258fcb9d96 Mon Sep 17 00:00:00 2001 From: "edward.zeng" Date: Fri, 3 Dec 2021 18:29:33 +0800 Subject: [PATCH] [skip ci] Refine drop collection design doc (#12715) Signed-off-by: Edward Zeng --- docs/design_docs/drop_collection_release_resources_en.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/design_docs/drop_collection_release_resources_en.md b/docs/design_docs/drop_collection_release_resources_en.md index 95b6a75f90..1dd1475d9b 100644 --- a/docs/design_docs/drop_collection_release_resources_en.md +++ b/docs/design_docs/drop_collection_release_resources_en.md @@ -29,11 +29,11 @@ DataNode ignites Flush&Drop Add a `dropped` flag in `SaveBinlogPathRequest` proto DN -- Flush all segment in this vChannel, When Flush&Drop, set the `dropped` flag true. +- Flush all segments in this vChannel, When Flush&Drop, set the `dropped` flag true. - If fails, retry at most 10 times and restart DC -- DataCoord marks segmentInfo as `dropped`, doesn't remove segmentInfos from Etcd +- DataCoord marks segmentInfo as `dropped`, doesn't remove segmentInfos from etcd - When recovery, check if the segments in the vchannel are all dropped - if not, recover before the drop - if so, no need to recover the vchannel