mirror of https://github.com/milvus-io/milvus.git
[skip ci]Improve guarantee ts works doc grammar (#11435)
Signed-off-by: tumao <yan.wang@zilliz.com>pull/11444/head
parent
3a65a4517c
commit
b36589308f
|
@ -33,7 +33,7 @@ Milvus uses timestamp and timetick watermark to ensure the consistency of the re
|
|||
|
||||
As shown in the figure below, when inserting data into the message queue, Milvus will not only time stamp these inserted
|
||||
records, but also insert timetick continuously. Taking "syncTs1" in the figure as an example, when downstream consumers
|
||||
(such as QueryNodes) see syncTs1, it means that all the data which is previous before syncTs1 has been consumed. In
|
||||
(such as QueryNodes) see syncTs1, it means that all the data which is earlier than syncTs1 has been consumed. In
|
||||
other words, the inserted record with a timestamp smaller than syncTs1 will no longer appear in the message queue.
|
||||
Of course, if there is, there must be a bug in the system. If you find it, we are pleased to solve it as soon as
|
||||
possible.
|
||||
|
|
Loading…
Reference in New Issue