# Timeout exception with many time-based indices after 00:00

**URL:** <https://discuss.elastic.co/t/timeout-exception-with-many-time-based-indices-after-00-00/63340>\
**Category:** Elasticsearch\
**Created:** [October 19, 2016, 1:45am UTC](https://discuss.elastic.co/t/timeout-exception-with-many-time-based-indices-after-00-00/63340 "2016-10-19T01:45:42Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![ogibayashi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ogibayashi/32/32299_2.png) [@ogibayashi](https://discuss.elastic.co/u/ogibayashi)\
**Post date:** [October 19, 2016, 1:45am UTC](https://discuss.elastic.co/t/timeout-exception-with-many-time-based-indices-after-00-00/63340/1 "2016-10-19T01:45:42Z")

</div>

Hello,

I am putting various kind of logs into Elasticsearch with daily time-based index (somedata-YYYY.MM.DD).  
Recently, I have started to put many other kind of logs into ES, then ES started to logs many ProcessClusterEventTimeoutException after 00:00 AM.

```
[2016-10-19 00:00:30,858][DEBUG][action.admin.indices.mapping.put] [myhostname] failed to put mappings on indices [[somedata-2016.10.18]], type [fluentd]

```

ProcessClusterEventTimeoutException[failed to process cluster event (put-mapping [fluentd]) within 30s]  
at org.elasticsearch.cluster.service.InternalClusterService$2$1.run(InternalClusterService.java:349)  
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)  
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)  
at java.lang.Thread.run(Thread.java:745)

Actually, I have more than 200 indices every day, so when the date changes, almost all of them will need new index for the next day.

I suspected that some node (maybe master node) was under high CPU load, but as show below, CPU usage is under 5% in all nodes(servers), and CPU usage is dropped during this time period (00:00-00:10 AM)

 ![](https://us1.discourse-cdn.com/elastic/original/2X/c/c13d5a75cf1882f5594ecfd68e6027a410e8ece5.png)

It seems like ES is not under high load but something is blocking the operation. Does anyone suggest how can I investigate this?

By the way, I am running 10 nodes Elasticsearch cluster with version 2.4.0.

Regards,  
Hironori

---

_[View the full topic](https://discuss.elastic.co/t/timeout-exception-with-many-time-based-indices-after-00-00/63340)._