admin/milvus
1
0
Fork 0
mirror of https://gitee.com/milvus-io/milvus.git synced 2026-01-07 19:31:51 +08:00
Code Issues Packages Projects Releases Wiki Activity
milvus/internal/datanode
History
yihao.dai 9e8cafcbe2
enhance: Skip loading bf in datanode (#36367) 
Skip loading bf in datanode:
1. When watching vchannels, skip loading bloom filters for segments.
2. Bypass bloom filter checks for delete messages, directly writing to
L0 segments.
3. Remove flushed segments proactively after flush.

issue: https://github.com/milvus-io/milvus/issues/34585

---------

Signed-off-by: bigsheeper <yihao.dai@zilliz.com>
2024-09-26 10:11:15 +08:00
..
allocator
Replace manual composed grpc call with Broker methods (#27676)
2023-10-13 09:55:34 +08:00
channel
fix: Use correct release func when datanode unwatch a channel (#35655)
2024-08-23 14:09:03 +08:00
compaction
feat: support embedding bm25 sparse vector and flush bm25 stats log (#36036)
2024-09-19 10:57:12 +08:00
importv2
feat: support embedding bm25 sparse vector and flush bm25 stats log (#36036)
2024-09-19 10:57:12 +08:00
iterators
enhance: Add ctx in SyncTask.Run to be cancellable (#34042)
2024-06-25 14:22:04 +08:00
util
enhance: Implement flusher in streamingNode (#34942)
2024-08-02 18:30:23 +08:00
data_node_test.go
enhance: Implement flusher in streamingNode (#34942)
2024-08-02 18:30:23 +08:00
data_node.go
enhance: Skip loading bf in datanode (#36367)
2024-09-26 10:11:15 +08:00
metrics_info.go
enhance: Implement flusher in streamingNode (#34942)
2024-08-02 18:30:23 +08:00
OWNERS
[skip ci]Update OWNERS files (#11898)
2021-11-16 15:41:11 +08:00
README.md
[skip ci]Change uppercase of MinIO (#9539)
2021-10-09 11:22:58 +08:00
services_test.go
feat: support embedding bm25 sparse vector and flush bm25 stats log (#36036)
2024-09-19 10:57:12 +08:00
services.go
enhance: Rename preAllocatedSegments (#35871)
2024-09-01 17:09:01 +08:00

README.md

Data Node

DataNode is the component to write insert and delete messages into persistent blob storage, for example MinIO or S3.

Dependency

  • KV store: a kv store that persists messages into blob storage.
  • Message stream: receive messages and publish imformation
  • Root Coordinator: get the latest unique IDs.
  • Data Coordinator: get the flush information and which message stream to subscribe.