# Elastic search getting timeout **URL:** \ **Category:** Elasticsearch\ **Created:** [January 5, 2017, 1:26am UTC](https://discuss.elastic.co/t/elastic-search-getting-timeout/70624 "2017-01-05T01:26:54Z")\ **Posts on this page:** 14\ **Page:** 1
**Author:** ![dubul](https://avatars.discourse-cdn.com/v4/letter/d/9f8e36/32.png) [@dubul](https://discuss.elastic.co/u/dubul)\ **Post date:** [January 5, 2017, 1:26am UTC](https://discuss.elastic.co/t/elastic-search-getting-timeout/70624/1 "2017-01-05T01:26:54Z")
Here is the error i'm getting, I have no clue about this error. Can anyone help me why this is erroring out. 2017-01-04 17:19:24,207][WARN][rest.suppressed] /logs-2017.01.05/logEvent Params: {index=logs-2017.01.05, type=logEvent} MasterNotDiscoveredException[null] at org.elasticsearch.action.support.master.TransportMasterNodeAction$AsyncSingleAction$5.onTimeout(TransportMasterNodeAction.java:226) at org.elasticsearch.cluster.ClusterStateObserver$ObserverClusterStateListener.onTimeout(ClusterStateObserver.java:236) at org.elasticsearch.cluster.service.InternalClusterService$NotifyTimeout.run(InternalClusterService.java:804) 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) ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [January 5, 2017, 1:38am UTC](https://discuss.elastic.co/t/elastic-search-getting-timeout/70624/2 "2017-01-05T01:38:48Z")
What version? What does your config look like? ---
**Author:** ![dubul](https://avatars.discourse-cdn.com/v4/letter/d/9f8e36/32.png) [@dubul](https://discuss.elastic.co/u/dubul)\ **Post date:** [January 5, 2017, 1:39am UTC](https://discuss.elastic.co/t/elastic-search-getting-timeout/70624/3 "2017-01-05T01:39:25Z")
@warkolm i'm using 2.3.3 ``` # ======================== 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: elk # # ------------------------------------ Node ------------------------------------ # # Use a descriptive name for the node: # node.name: dt1esp01p03 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: dt1esp01p03 # # 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: ["dt1esp01p02", "dt1esp01p01", "dt1esp01p03"] # # 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:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [January 5, 2017, 1:56am UTC](https://discuss.elastic.co/t/elastic-search-getting-timeout/70624/4 "2017-01-05T01:56:39Z")
You need to remove the spaces in front of all your config lines. ---
**Author:** ![dubul](https://avatars.discourse-cdn.com/v4/letter/d/9f8e36/32.png) [@dubul](https://discuss.elastic.co/u/dubul)\ **Post date:** [January 5, 2017, 1:58am UTC](https://discuss.elastic.co/t/elastic-search-getting-timeout/70624/5 "2017-01-05T01:58:44Z")
I dont think its a space issue. It was working fine from 5 months until last week ---
**Author:** ![wenpos](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/wenpos/32/15326_2.png) [@wenpos](https://discuss.elastic.co/u/wenpos)\ **Post date:** [January 5, 2017, 3:13am UTC](https://discuss.elastic.co/t/elastic-search-getting-timeout/70624/7 "2017-01-05T03:13:29Z")
it looks like your master node is out of service. is your cluster is green or at least yellow? ---
**Author:** ![dubul](https://avatars.discourse-cdn.com/v4/letter/d/9f8e36/32.png) [@dubul](https://discuss.elastic.co/u/dubul)\ **Post date:** [January 5, 2017, 8:04am UTC](https://discuss.elastic.co/t/elastic-search-getting-timeout/70624/8 "2017-01-05T08:04:55Z")
The cluster looks in red ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [January 5, 2017, 8:12am UTC](https://discuss.elastic.co/t/elastic-search-getting-timeout/70624/9 "2017-01-05T08:12:42Z")
What is the output from the [cat nodes API](https://www.elastic.co/guide/en/elasticsearch/reference/2.2/cat-nodes.html)? ---
**Author:** ![dubul](https://avatars.discourse-cdn.com/v4/letter/d/9f8e36/32.png) [@dubul](https://discuss.elastic.co/u/dubul)\ **Post date:** [January 5, 2017, 8:35am UTC](https://discuss.elastic.co/t/elastic-search-getting-timeout/70624/10 "2017-01-05T08:35:17Z")
@Christian_Dahlqvist @wenpos[http://localhost:9200/\_cat/nodes](http://localhost:9200/_cat/nodes) is loading, but does not show any stats of nodes. I have attached the cluster health ![](https://us1.discourse-cdn.com/elastic/original/2X/0/097a2f5e3c7d5931bc44aad61bfa99ecb21740ea.png) ---
**Author:** ![dubul](https://avatars.discourse-cdn.com/v4/letter/d/9f8e36/32.png) [@dubul](https://discuss.elastic.co/u/dubul)\ **Post date:** [January 5, 2017, 8:46am UTC](https://discuss.elastic.co/t/elastic-search-getting-timeout/70624/11 "2017-01-05T08:46:27Z")
Here is the \_cat/nodes output 10.90.88.16 10.90.88.16 67 63 -1.00 d \* dt1esp01p01 10.90.88.11 10.90.88.11 74 68 -1.00 d m dt1esp01p03 10.90.88.17 10.90.88.17 35 60 -1.00 d m dt1esp01p02 ---
**Author:** ![wenpos](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/wenpos/32/15326_2.png) [@wenpos](https://discuss.elastic.co/u/wenpos)\ **Post date:** [January 5, 2017, 9:32am UTC](https://discuss.elastic.co/t/elastic-search-getting-timeout/70624/12 "2017-01-05T09:32:01Z")
all the shards recovery ？the search action may based on those shards. ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [January 5, 2017, 9:36am UTC](https://discuss.elastic.co/t/elastic-search-getting-timeout/70624/13 "2017-01-05T09:36:17Z")
That looks like a very large number of shards for a 3 node cluster. What is your average shard size? How much heap does each node have? ---
**Author:** ![dubul](https://avatars.discourse-cdn.com/v4/letter/d/9f8e36/32.png) [@dubul](https://discuss.elastic.co/u/dubul)\ **Post date:** [January 5, 2017, 5:11pm UTC](https://discuss.elastic.co/t/elastic-search-getting-timeout/70624/14 "2017-01-05T17:11:52Z")
Shard size is 5 per index with one replica ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [February 2, 2017, 5:12pm UTC](https://discuss.elastic.co/t/elastic-search-getting-timeout/70624/15 "2017-02-02T17:12:00Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.