# Leap Year Issue: Performance issue

**URL:** <https://discuss.elastic.co/t/leap-year-issue-performance-issue/221897>\
**Category:** Elasticsearch\
**Created:** [March 3, 2020, 1:52pm UTC](https://discuss.elastic.co/t/leap-year-issue-performance-issue/221897 "2020-03-03T13:52:02Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Nitin\_K](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nitin_k/32/46090_2.png) [@Nitin\_K](https://discuss.elastic.co/u/Nitin_K)\
**Post date:** [March 3, 2020, 1:52pm UTC](https://discuss.elastic.co/t/leap-year-issue-performance-issue/221897/1 "2020-03-03T13:52:02Z")

</div>

Hi, We are using ElasticSearch 6.2 in production. We noticed a spike in search latency on the recent leap day (02/29/2020).

We use lot of date\_range and date fields in our index. We noticed that our search latency almost tripled on the 29th exactly from 00:00:00 (and CPU spiked to 100% as well) and lasted only for the 29th.

Our search rate and index rate was unchanged during the day, and there was no change in query/index fields. This leads us to believe there is something internally in ES which caused this issue.

Is there anything internally in ES that can cause this?

---

<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:** [March 31, 2020, 1:52pm UTC](https://discuss.elastic.co/t/leap-year-issue-performance-issue/221897/2 "2020-03-31T13:52:03Z")

</div>

Closed on March 31, 2020, 1:52pm UTC

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