Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Bug]: [ResourceGroup]get_replicas does not print the resource group info #22220

Closed
1 task done
yanliang567 opened this issue Feb 16, 2023 · 4 comments · Fixed by milvus-io/pymilvus#1307
Closed
1 task done

[Bug]: [ResourceGroup]get_replicas does not print the resource group info #22220

yanliang567 opened this issue Feb 16, 2023 · 4 comments · Fixed by milvus-io/pymilvus#1307
Assignees
@yanliang567 @weiliu1031
Labels
kind/bug Issues or changes related a bug triage/accepted Indicates an issue or PR is ready to be actively worked on.
Milestone
2.3

Comments

@yanliang567
Copy link
Contributor

Is there an existing issue for this?

  • I have searched the existing issues

Environment

- Milvus version: master-20230216-8ec5ba13
- Deployment mode(standalone or cluster): cluster
- MQ type(rocksmq, pulsar or kafka):    
- SDK version(e.g. pymilvus v2.0.0rc2):  pymilvus-2.3.0.dev38

Current Behavior

>>> replicas.groups[0]
Group: <group_id:439354864989634571>, <group_nodes:(46,)>, <shards:[Shard: <channel_name:yanliang-master-rg-rootcoord-dml_38_439354863437624222v0>, <shard_leader:46>, <shard_nodes:[46, 46, 46]>, Shard: <channel_name:yanliang-master-rg-rootcoord-dml_39_439354863437624222v1>, <shard_leader:46>, <shard_nodes:[46, 46, 46]>]>

Expected Behavior

print the resource group related info

>>> replicas.groups[0].resource_group
'__default_resource_group'
>>> replicas.groups[0].num_outbound_node
{}

Steps To Reproduce

No response

Milvus Log

No response

Anything else?

No response
@yanliang567 yanliang567 added kind/bug Issues or changes related a bug needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Feb 16, 2023
@yanliang567 yanliang567 self-assigned this Feb 16, 2023
@yanliang567
Copy link
Contributor Author

/assign @weiliu1031
/unassign

@yanliang567 yanliang567 added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Feb 16, 2023
@yanliang567 yanliang567 modified the milestones: 2.2.4, 2.3 Feb 16, 2023
@yanliang567
Copy link
Contributor Author

/assign @weiliu1031

@yanliang567
Copy link
Contributor Author

i am running on dev38 already

@weiliu1031 weiliu1031 mentioned this issue Feb 16, 2023
Merged
@yanliang567
Copy link
Contributor Author

verified on pymilvus 2.3.0.dev44

yanliang567 added a commit that referenced this issue May 6, 2023
@yanliang567
Sync tests from master
bce6348 
related issue: ##22220
@yanliang567 yanliang567 mentioned this issue May 6, 2023
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@yanliang567 yanliang567

@weiliu1031 weiliu1031

Labels
kind/bug Issues or changes related a bug triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Milestone
2.3
Development

Successfully merging a pull request may close this issue.

expose rg info weiliu1031/pymilvus
2 participants
@yanliang567 @weiliu1031