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
Watching the topk dashboard, I noticed that very high traffic sites, maa.. mnl.., appear to have a gradual memory leak for all sidecar services that is not observed at other sites.
Image include reset during rollout on 07/08
The text was updated successfully, but these errors were encountered:
There may indeed be a memory leak, but one other factor probably contributing to the unusually high load at MAA01, is that MAA02 has been down for the past couple weeks, meaning that MAA01 has to carry the whole load for that region.
gru is also one of our busiest metros. If there is a leak, it seems more likely to be triggered in busy locations. It's possible the leak is very slow at other locations.
Watching the topk dashboard, I noticed that very high traffic sites, maa.. mnl.., appear to have a gradual memory leak for all sidecar services that is not observed at other sites.
Image include reset during rollout on 07/08
The text was updated successfully, but these errors were encountered: