Details
-
Bug
-
Resolution: Fixed
-
Major
-
4.6.3
Description
As seen in one of the customer memory profiles, /getIndexStatus can generate huge amount of garbage as it initializes a new ClusterInfoCache every time it gets invoked and ns-server calls this every 1 second.
The memory profile is attached.
It would be good to cache the ClusterInfoCache results.
Attachments
Issue Links
- relates to
-
MB-26671 Optimize garbage generated by /getIndexStatus
- Resolved