# Possible Bug: Request Cache Stats remain all zeros since upgrading to 6.3.1

**URL:** <https://discuss.elastic.co/t/possible-bug-request-cache-stats-remain-all-zeros-since-upgrading-to-6-3-1/141069>\
**Category:** Elasticsearch\
**Created:** [July 23, 2018, 3:39am UTC](https://discuss.elastic.co/t/possible-bug-request-cache-stats-remain-all-zeros-since-upgrading-to-6-3-1/141069 "2018-07-23T03:39:53Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![kwu](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kwu/32/14714_2.png) [@kwu](https://discuss.elastic.co/u/kwu)\
**Post date:** [July 23, 2018, 3:39am UTC](https://discuss.elastic.co/t/possible-bug-request-cache-stats-remain-all-zeros-since-upgrading-to-6-3-1/141069/1 "2018-07-23T03:39:54Z")

</div>

Since upgrading one of our production cluster from 6.2.4 to 6.3.1 , the monitoring systems showing all Request Cache Stats as zeros, including cache size/hit/miss/evict ,etc. These stats are collected from node stats api and I verified the stats by manually calling the api which gives me the same result.

I am sure we constantly have queries that involve Request Cache actions and all stats remaining at zero makes no sense. What I am not sure however is if there there is possibly a bug within the cache module or monitoring module?

Any advice is high appreciated!

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [August 20, 2018, 3:51am UTC](https://discuss.elastic.co/t/possible-bug-request-cache-stats-remain-all-zeros-since-upgrading-to-6-3-1/141069/2 "2018-08-20T03:51:35Z")

</div>

Closed on August 20, 2018, 3:51am UTC

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.