# None of the configured nodes are available

**URL:** <https://discuss.elastic.co/t/none-of-the-configured-nodes-are-available/330340>\
**Category:** Elasticsearch\
**Created:** [April 20, 2023, 1:53am UTC](https://discuss.elastic.co/t/none-of-the-configured-nodes-are-available/330340 "2023-04-20T01:53:28Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![zz-GuoYF](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zz-guoyf/32/119988_2.png) [@zz-GuoYF](https://discuss.elastic.co/u/zz-GuoYF)\
**Post date:** [April 20, 2023, 1:53am UTC](https://discuss.elastic.co/t/none-of-the-configured-nodes-are-available/330340/1 "2023-04-20T01:53:28Z")

</div>

The version of Elasticsearch I used is 2.4.6 and the deployment mode is single-node es.  
When I was running a query with a data volume of 7 million, the following error occurred in es：

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/c/6/c6a2815b33d383379e342ef8e652d11fa54d9e03.png)  
In addition, by adding GC log parameters, it is found that when problems occur, es is undergoing Full GC at this time, and the CMS collector is degraded to the Serial collector.  
 ![image](https://us1.discourse-cdn.com/elastic/original/3X/b/8/b8b484c015a7a167a4fc6416abff62669766ab67.png)  
Is there any way I can solve this problem?

---

<div class="post-metadata">

**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:** [April 20, 2023, 2:08am UTC](https://discuss.elastic.co/t/none-of-the-configured-nodes-are-available/330340/2 "2023-04-20T02:08:31Z")

</div>

Welcome to our community! 😃

Please don't post pictures of text, logs or code. They are difficult to read, impossible to search and replicate (if it's code), and some people may not be even able to see them 🙂

---

<div class="post-metadata">

**Author:** ![zz-GuoYF](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zz-guoyf/32/119988_2.png) [@zz-GuoYF](https://discuss.elastic.co/u/zz-GuoYF)\
**Post date:** [April 20, 2023, 2:12am UTC](https://discuss.elastic.co/t/none-of-the-configured-nodes-are-available/330340/3 "2023-04-20T02:12:04Z")

</div>

Sorry, because my code error is in the Intranet environment, I cannot copy the error log, so I have to put up the error screenshot.

---

<div class="post-metadata">

**Author:** ![zz-GuoYF](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zz-guoyf/32/119988_2.png) [@zz-GuoYF](https://discuss.elastic.co/u/zz-GuoYF)\
**Post date:** [April 25, 2023, 8:35am UTC](https://discuss.elastic.co/t/none-of-the-configured-nodes-are-available/330340/4 "2023-04-25T08:35:58Z")

</div>

I resolved the problem by using a retry mechanism. The specific code is as follows：

```auto
for (int i = 0; i < 10; i++) {
    try{
        // may throw exception code
        // xxxxxxxx
        break;
    } catch (Exception e) {
        if (i < 9) {
            System.out.println("handle with es occur exception, wait ande continut" + i);
            System.out.println("exception is:" + e.printStrace());
            Thread.sleep(10000L);
        }
    }
}

```

---

<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:** [May 23, 2023, 8:36am UTC](https://discuss.elastic.co/t/none-of-the-configured-nodes-are-available/330340/5 "2023-05-23T08:36:19Z")

</div>

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