mirror of https://github.com/milvus-io/milvus.git
parent
a78b2010e9
commit
3a36aee223
|
@ -155,7 +155,7 @@ allocation logic of segment ID is the responsibility of the Data Coordinator. Th
|
||||||
written needs to be determined before writing to DmChannel. For a write operation, the proxy will hash each row of data
|
written needs to be determined before writing to DmChannel. For a write operation, the proxy will hash each row of data
|
||||||
again according to the hash value of its primary key, and then determine into which DmChannel each row of data enters. After
|
again according to the hash value of its primary key, and then determine into which DmChannel each row of data enters. After
|
||||||
collecting the number of pieces to be written by each DmChannel, apply to the data coordinator for which SegmentIDs the
|
collecting the number of pieces to be written by each DmChannel, apply to the data coordinator for which SegmentIDs the
|
||||||
newly written data of these dmchannels belong. In the specific implementation, the proxy need to preallocate some
|
newly written data of these dmchannels belong. In the specific implementation, the proxy needs to preallocate some
|
||||||
quotas to the Data Coordinator to avoid frequent direct GRPC communication with the Data Coordinator.
|
quotas to the Data Coordinator to avoid frequent direct GRPC communication with the Data Coordinator.
|
||||||
|
|
||||||
One consideration for uniformly assigning SegmentIDs by Data Coordinator is that Data Coordinator is responsible for
|
One consideration for uniformly assigning SegmentIDs by Data Coordinator is that Data Coordinator is responsible for
|
||||||
|
|
Loading…
Reference in New Issue