From cd36d3ffdfff5b1dc25e77addcae3f0de1af955d Mon Sep 17 00:00:00 2001 From: yanliang567 <82361606+yanliang567@users.noreply.github.com> Date: Fri, 24 Dec 2021 16:40:19 +0800 Subject: [PATCH] [skip e2e]Update Proxy name (#14162) Signed-off-by: yanliang567 --- docs/design_docs/proxy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/design_docs/proxy.md b/docs/design_docs/proxy.md index a6081eedac..540d74631b 100644 --- a/docs/design_docs/proxy.md +++ b/docs/design_docs/proxy.md @@ -360,7 +360,7 @@ members minTs and maxTs, which respectively represent the minimum and maximum ti completed on pChan. The channelsTimeTicker collects timestamp information mainly depends on this method. The awakened coroutine reduces the timestamp result and sends the final timestamp result back to the RootCoord. -taskScheduler is also responsible for collecting the results of search requests. For each search request, when the proxy +taskScheduler is also responsible for collecting the results of search requests. For each search request, when Proxy writes the request to the DqRequestChannel, it will attach the ReqID, and the query nodes will also bring the ReqID back when writing the search result back to the DqResultChannel. taskScheduler will start a background coroutine to consume search result from DqResultChannel, and then distribute messages according to the ReqID in it. When several results of