Closed zhuwenxing closed 1 year ago
It is a stable reproduced issue, so set it as critical
/assign @congqixia
ok, working on it /unassign @yanliang567
This bug is caused by adding queryshard
and setup shard cluster
happens in different stage of WatchDmChannel
task execution.
When fetching data distribution, either condition needs to be checked before calling ShardCluster.GetSegmentInfos
Could your please check whether bug persists after patch merged? /assign @zhuwenxing
verified and passed with 2.2.0-20230222-40878a86
Is there an existing issue for this?
Environment
Current Behavior
querynode panic
Expected Behavior
No response
Steps To Reproduce
No response
Milvus Log
failed job: https://qa-jenkins.milvus.io/blue/organizations/jenkins/deploy_test_for_release_cron/detail/deploy_test_for_release_cron/386/pipeline log:
artifacts-pulsar-cluster-upgrade-386-server-logs (1).tar.gz artifacts-pulsar-cluster-upgrade-386-pytest-logs.tar.gz
Anything else?
No response