[Bug]: Add Tickle logic in channel reassign #21074
Labels
kind/enhancement
Issues or changes related to enhancement
severity/critical
Critical, lead to crash, data missing, wrong result, function totally doesn't work.
stale
indicates no udpates for 30 days
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
Milestone
Is there an existing issue for this?
Environment
Current Behavior
Current Data coord send a channel watch to datanode, and wait for Params.DataCoordCfg.MaxWatchDuration time before it decide to reassign the channel to another. datanode.
This may cause serious issues, especially when watch channel takes lager than Params.DataCoordCfg.MaxWatchDuration(happens on the case where there are many stats logs).
Expected Behavior
Datanode keep modifying etcd path(Tickle), so datacoord won't timeout the assign, after tickle datacoord will only reset timeout and continue.
Thinks of some way to improve stats log load. This becomes a serious issue when data channel becomes huge.
Steps To Reproduce
No response
Milvus Log
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: