Why are some call graph in cluster-trace-microservices-v2021 disconnected?
Hi,
I was analyzing the call graphs and found that some call graphs are disconnected. How is this possible?
For example, in the above figure, node 205 is a separate island. Note that the numbering (for example, 205) is something that I have added so please do not be confused by this.
Thanks, Kapil
Also, after I construct a call graph like above, just by looking at the topology of the graph, can we deduce that node 41 (in the above figure) is the source node or an entering microservice?
Thank you for your interest. We have identified that some call metrics were missed in the production cluster, resulting in the disconnection of certain nodes, such as node 205 in the figure. Additionally, as you have noticed, node 41 is the entering microservice of the call graph.
Hi kapilagrawal95, we faced the same problem in a work done recently. We created a matlab script that is a kind of cleaning procedure that removes unconnected traces. The code is here, https://github.com/mSvcBench/muBench/tree/main/examples/Alibaba/Matlab
Thanks @andreadetti, I will look into this.