Open binbinlv opened 7 months ago
And the executing plan number is strange:
c.get_compaction_state(is_major=True)
CompactionState
- compaction id: 449137408157615384
- State: Executing
- executing plan number: 86
- timeout plan number: 0
- complete plan number: 6
>>>
>>>
>>> c.get_compaction_state(is_major=True)
CompactionState
- compaction id: 449137408157615384
- State: Executing
- executing plan number: 144
- timeout plan number: 0
- complete plan number: 16
>>>
>>>
>>> c.get_compaction_state(is_major=True)
CompactionState
- compaction id: 449137408157615384
- State: Executing
- executing plan number: 163
- timeout plan number: 0
- complete plan number: 22
>>>
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Rotten issues close after 30d of inactivity. Reopen the issue with /reopen
.
keep it
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Rotten issues close after 30d of inactivity. Reopen the issue with /reopen
.
any updates for this
Is there an existing issue for this?
Environment
Current Behavior
Major compact hangs when enable "usePartitionKeyAsClusteringKey" and "useVectorAsClusteringKey" together with partition key field
Expected Behavior
Major compact successfully
Steps To Reproduce
Milvus Log
collection name: major_compaction_collection_enable_scalar_partition_key_after_index
https://grafana-4am.zilliz.cc/explore?orgId=1&left=%7B%22datasource%22:%22Loki%22,%22queries%22:%5B%7B%22refId%22:%22A%22,%22expr%22:%22%7Bcluster%3D%5C%22devops%5C%22,namespace%3D%5C%22chaos-testing%5C%22,pod%3D~%5C%22major-vec-partition-vabea.*%5C%22%7D%22%7D%5D,%22range%22:%7B%22from%22:%22now-1h%22,%22to%22:%22now%22%7D%7D
Anything else?
No response