# Elastic search is failing to perform bulk index
**URL:** https://discuss.elastic.co/t/elastic-search-is-failing-to-perform-bulk-index/70306
**Category:** Elasticsearch
**Created:** [December 31, 2016, 12:52am UTC](https://discuss.elastic.co/t/elastic-search-is-failing-to-perform-bulk-index/70306 "2016-12-31T00:52:48Z")
**Posts on this page:** 8
**Page:** 1
### Author:  [@dubul](https://discuss.elastic.co/u/dubul)
#### Post date: [December 31, 2016, 12:52am UTC](https://discuss.elastic.co/t/elastic-search-is-failing-to-perform-bulk-index/70306/1 "2016-12-31T00:52:48Z")
I'm using filebeat to ship the logs to elastic search. I have noticed that its failing to index the logs from 2 weeks.
File beat error:
ERR Failed to perform any bulk index operations: Post [http://dt1es01p02:9200/\_bulk:](http://dt1es01p02:9200/_bulk:) net/http: request canceled (Client.Timeout exceeded while awaiting headers)
Elastic search log:
[DEBUG][action.admin.indices.create] [dt1es01p02] [bit-logs-2016.12.30] failed to create
ProcessClusterEventTimeoutException[failed to process cluster event (create-index [bit-logs-2016.12.30], cause [auto(bulk api)]) within 1m]
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)
I'm not sure about this error, Is this something I need to change the config file in elasticsearch or filebeat.yaml?
How could I fix this issue? I've tried changing the bulk index,timeout, flush interval but no use
---
### Author:  [@dubul](https://discuss.elastic.co/u/dubul)
#### Post date: [December 31, 2016, 12:54am UTC](https://discuss.elastic.co/t/elastic-search-is-failing-to-perform-bulk-index/70306/2 "2016-12-31T00:54:32Z")
@iluvcode Any help?
---
### Author:  [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [December 31, 2016, 4:15am UTC](https://discuss.elastic.co/t/elastic-search-is-failing-to-perform-bulk-index/70306/3 "2016-12-31T04:15:19Z")
What state is your cluster in?
---
### Author:  [@dubul](https://discuss.elastic.co/u/dubul)
#### Post date: [December 31, 2016, 5:04am UTC](https://discuss.elastic.co/t/elastic-search-is-failing-to-perform-bulk-index/70306/4 "2016-12-31T05:04:14Z")
I didn't get you. Are you asking about health, its green.
---
### Author:  [@amar-tari](https://discuss.elastic.co/u/amar-tari)
#### Post date: [January 2, 2017, 11:32am UTC](https://discuss.elastic.co/t/elastic-search-is-failing-to-perform-bulk-index/70306/5 "2017-01-02T11:32:43Z")
Have you checked threadpool setting, Since you are using \_bulk API ,
Please try to increase it if possible.
[https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-threadpool.html](https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-threadpool.html)
---
### Author:  [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)
#### Post date: [January 2, 2017, 11:41am UTC](https://discuss.elastic.co/t/elastic-search-is-failing-to-perform-bulk-index/70306/6 "2017-01-02T11:41:44Z")
> [@dubul](#):
>
> [DEBUG][action.admin.indices.create] [dt1es01p02] [bit-logs-2016.12.30] failed to createProcessClusterEventTimeoutException[failed to process cluster event (create-index [bit-logs-2016.12.30], cause [auto(bulk api)]) within 1m]
It looks like it is timing out trying to create the new index. Which Elasticsearch version are you on? Do you have any non-default cluster settings? How large is your cluster? How many indices/shards do you have in the cluster?
---
### Author:  [@dubul](https://discuss.elastic.co/u/dubul)
#### Post date: [January 3, 2017, 5:50pm UTC](https://discuss.elastic.co/t/elastic-search-is-failing-to-perform-bulk-index/70306/7 "2017-01-03T17:50:12Z")
@Christian_Dahlqvist @amar-tari i'm using 2.3.3 version. Here is my config on node3, which is similar on other 2 nodes except the nodename and networkhost will different(i'e hostname is selected for nodename,networkhost)
```
# ======================== Elasticsearch Configuration =========================
#
# NOTE: Elasticsearch comes with reasonable defaults for most settings.
# Before you set out to tweak and tune the configuration, make sure you
# understand what are you trying to accomplish and the consequences.
#
# The primary way of configuring a node is via this file. This template lists
# the most important settings you may want to configure for a production cluster.
#
# Please see the documentation for further information on configuration options:
#
#
# ---------------------------------- Cluster -----------------------------------
#
# Use a descriptive name for your cluster:
#
cluster.name: elkdev
#
# ------------------------------------ Node ------------------------------------
#
# Use a descriptive name for the node:
#
node.name: dt1es01p03
node.master: true
node.data: true
#
# Add custom attributes to the node:
#
# node.rack: r1
#
# ----------------------------------- Paths ------------------------------------
#
# Path to directory where to store the data (separate multiple locations by comma):
#
path.data: e:\data
#
# Path to log files:
#
path.logs: e:\logs
#
# ----------------------------------- Memory -----------------------------------
#
# Lock the memory on startup:
#
bootstrap.mlockall: true
#
# Make sure that the `ES_HEAP_SIZE` environment variable is set to about half the memory
# available on the system and that the owner of the process is allowed to use this limit.
#
# Elasticsearch performs poorly when the system is swapping the memory.
#
# ---------------------------------- Network -----------------------------------
#
# Set the bind address to a specific IP (IPv4 or IPv6):
#
network.host: dt1es01p03
#
# Set a custom port for HTTP:
#
http.port: 9200
#
# For more information, see the documentation at:
#
#
# --------------------------------- Discovery ----------------------------------
#
# Pass an initial list of hosts to perform discovery when new node is started:
# The default list of hosts is ["127.0.0.1", "[::1]"]
#
discovery.zen.ping.unicast.hosts: ["dt1es01p01", "dt1es01p02", "dt1es01p03"]
#
# Prevent the "split brain" by configuring the majority of nodes (total number of nodes / 2 + 1):
#
discovery.zen.minimum_master_nodes: 2
#
# For more information, see the documentation at:
#
#
# ---------------------------------- Gateway -----------------------------------
#
# Block initial recovery after a full cluster restart until N nodes are started:
#
# gateway.recover_after_nodes: 3
#
# For more information, see the documentation at:
#
#
# ---------------------------------- Various -----------------------------------
#
# Disable starting multiple nodes on a single system:
#
# node.max_local_storage_nodes: 1
#
# Require explicit names when deleting indices:
#
# action.destructive_requires_name: true
```
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [January 31, 2017, 5:50pm UTC](https://discuss.elastic.co/t/elastic-search-is-failing-to-perform-bulk-index/70306/8 "2017-01-31T17:50:29Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.