Replies: 2 comments 5 replies
-
This is cool, I would like to add this later. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Beta Was this translation helpful? Give feedback.
5 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi !
What about adding a treemap showing the segments distribution among nodes ? The goal is to get a better view of the current situation and help understand why some querynodes are overloaded. Having the possibility directly move segment is a bonus.
Currently I'm able to do that using a Python script calling pymilvus utility.get_query_segment_info() and collection.get_replicas(), and generate a treemap view with plotly.express. I modified some javascript stuff inside to allow copy/paste the segment ID by right-click and call next manually call a move-segment.py script.
Treemap are interactive and use this logic :
The treemap by Collection add the "Replica_group" granularity to avoid error while trying to move segment on another node with a different replicas group.
"embedding_coll_x" are my anonymized collections ;)
by Collection
by Node
This is more or less something like the Elasticsearch Cerebro UI
You can have something similar with grafana, but it's not very usable.
Next I would like to add the memory usage per node and their total number of sealed segments to help me choose the right node to move the segment without switching with grafana.
Beta Was this translation helpful? Give feedback.
All reactions