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
The back story is that each volumedriver now has 2 proxies deployed. Each proxy contains statistics for a given set namespaces and without resetting the statistics, it will forever show the same statistics if a volume would move to another node/volumedriver and nothing would ever happen on a namespace on that proxy.
A possible solution would be to add a timestamp to tell us when the statistics were last updated or when the last get/put/delete/whatever was executed for that namespace on that proxy and give us an idea on how relevant the returned statistics are.
The text was updated successfully, but these errors were encountered:
The back story is that each volumedriver now has 2 proxies deployed. Each proxy contains statistics for a given set namespaces and without resetting the statistics, it will forever show the same statistics if a volume would move to another node/volumedriver and nothing would ever happen on a namespace on that proxy.
A possible solution would be to add a timestamp to tell us when the statistics were last updated or when the last get/put/delete/whatever was executed for that namespace on that proxy and give us an idea on how relevant the returned statistics are.
The text was updated successfully, but these errors were encountered: