You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 :
Treemap by Node: 'All', 'Node', 'Collection', 'Segment_Type', 'Segment_ID',
Treemap by Collection: 'All', 'Collection', 'Group_ID', 'Node', 'Segment_ID'
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.
The text was updated successfully, but these errors were encountered:
Discussed in #530
Originally posted by Archalbc June 7, 2024
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.
The text was updated successfully, but these errors were encountered: