History

congqixia 2e6ddd7f2a Add datanode&channel match check for Flush (#19985 ) Signed-off-by: Congqi Xia <congqi.xia@zilliz.com> Signed-off-by: Congqi Xia <congqi.xia@zilliz.com>		2022-10-22 12:09:28 +08:00
..
OWNERS	…
README.md	…
allocator.go	…
allocator_test.go	…
channel_checker.go	…
channel_checker_test.go	…
channel_manager.go	…
channel_manager_factory.go	…
channel_manager_test.go	…
channel_store.go	…
channel_store_test.go	…
cluster.go	…
cluster_test.go	…
compaction.go	…
compaction_test.go	…
compaction_trigger.go	…
compaction_trigger_test.go	…
const.go	…
errors.go	…
errors_test.go	…
garbage_collector.go	…
garbage_collector_test.go	…
handler.go	…
meta.go	…
meta_test.go	…
meta_util.go	…
metrics_info.go	…
metrics_info_test.go	…
mock_test.go	…
policy.go	…
policy_test.go	…
segment_allocation_policy.go	…
segment_allocation_policy_test.go	…
segment_info.go	…
segment_manager.go	…
segment_manager_test.go	…
segment_reference_manager.go	…
segment_reference_manager_test.go	…
server.go	…
server_test.go	…
services.go	…
session.go	…
session_manager.go	…
util.go	…
util_test.go	…

Data Coordinator

Data cooridnator(datacoord for short) is the component to organize DataNodes and segments allocations.

Dependency

KV store: a kv store has all the meta info datacoord needs to operate. (etcd)
Message stream: a message stream to communicate statistics information with data nodes. (Pulsar)
Root Coordinator: timestamp, id and meta source.
Data Node(s): could be an instance or a cluster, actual worker group handles data modification operations.