After we swap the catalog indexes, we would expect that since the old index is no longer being used, its cache stops taking up a lot of the heap. That way, we can use the heap more effectively for indexes that are actually being used.
Actual behavior
The filter, document, and query cache are still there for several days, even though the index is not being used(!)
Date
Filter cache size for catalog-alma-production2
Document cache size for catalog-alma-production2
Query result cache size for catalog-alma-production2
28 May (when we moved catalog-alma-production2 out of production)
982
2723
752
29 May
976
2931
750
30 May
844
2585
651
31 May
844
2585
651
1 Jun
844
2585
651
2 Jun
844
2585
651
3 Jun
844
2585
651
Steps to replicate
Go to this little dashboard and choose different days, and look at the cache size info.
Expected behavior
After we swap the catalog indexes, we would expect that since the old index is no longer being used, its cache stops taking up a lot of the heap. That way, we can use the heap more effectively for indexes that are actually being used.
Actual behavior
The filter, document, and query cache are still there for several days, even though the index is not being used(!)
Steps to replicate
Go to this little dashboard and choose different days, and look at the cache size info.
Impact of this bug
High heap usage, lower performance.