# Client-only routing specified but no client nodes with HTTP-enabled were found in the cluster

**URL:** <https://discuss.elastic.co/t/client-only-routing-specified-but-no-client-nodes-with-http-enabled-were-found-in-the-cluster/167466>\
**Category:** Elasticsearch\
**Tags:** es-hadoop\
**Created:** [February 7, 2019, 2:10pm UTC](https://discuss.elastic.co/t/client-only-routing-specified-but-no-client-nodes-with-http-enabled-were-found-in-the-cluster/167466 "2019-02-07T14:10:36Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![saklar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/saklar/32/40680_2.png) [@saklar](https://discuss.elastic.co/u/saklar)\
**Post date:** [February 7, 2019, 2:10pm UTC](https://discuss.elastic.co/t/client-only-routing-specified-but-no-client-nodes-with-http-enabled-were-found-in-the-cluster/167466/1 "2019-02-07T14:10:36Z")

</div>

Hİ,

We have elasticsearch 6.5.4 version and Cloudera 5.4.7-1 version. We installed elasticsearch-hadoop-2.1.1.jar to connect between hdfs and elasticsearch. Then the hive table below were created to fetch the data from elasticsearch.

```
CREATE EXTERNAL TABLE TEST_ES_TBL (
    st string)
STORED BY 'org.elasticsearch.hadoop.hive.EsStorageHandler'
TBLPROPERTIES('es.nodes' = '10.51.29.105', 'es.port' = '9200', 'es.resource' = 'test/docs',
              'es.mapping.names' = 'st: str', 'es.index.auto.create'='true'); 

```

But it gives the error like that;

`java.io.IOException: org.elasticsearch.hadoop.EsHadoopIllegalArgumentException: Client-only routing specified but no client nodes with HTTP-enabled were found in the cluster...`

We also set the "es.nodes.client.only" = "true" but nothing happens. Can you help us to solve the problem, please? What is the point we miss?

Any help would be appreciated. Thanks.

---

<div class="post-metadata">

**Author:** ![james.baiera](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/james.baiera/32/10209_2.png) [@james.baiera](https://discuss.elastic.co/u/james.baiera)\
**Post date:** [February 11, 2019, 9:45pm UTC](https://discuss.elastic.co/t/client-only-routing-specified-but-no-client-nodes-with-http-enabled-were-found-in-the-cluster/167466/2 "2019-02-11T21:45:37Z")

</div>

I would double check your hive and hadoop settings to see if there are any properties that enable client-only routing. Something in the deployment is setting that property and it's getting into the storage handler, thus causing errors in the submission of the query.

---

<div class="post-metadata">

**Author:** ![saklar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/saklar/32/40680_2.png) [@saklar](https://discuss.elastic.co/u/saklar)\
**Post date:** [February 12, 2019, 11:46am UTC](https://discuss.elastic.co/t/client-only-routing-specified-but-no-client-nodes-with-http-enabled-were-found-in-the-cluster/167466/3 "2019-02-12T11:46:52Z")

</div>

Is there any suggestion to look a specific parameter or settings file to find out the error?

I'm looking to elasticsearch.yml but nothing found.

Thanks.

---

<div class="post-metadata">

**Author:** ![james.baiera](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/james.baiera/32/10209_2.png) [@james.baiera](https://discuss.elastic.co/u/james.baiera)\
**Post date:** [February 15, 2019, 4:59pm UTC](https://discuss.elastic.co/t/client-only-routing-specified-but-no-client-nodes-with-http-enabled-were-found-in-the-cluster/167466/4 "2019-02-15T16:59:55Z")

</div>

These would be settings in your Hadoop configurations or in your Hive configurations

---

<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 15, 2019, 4:59pm UTC](https://discuss.elastic.co/t/client-only-routing-specified-but-no-client-nodes-with-http-enabled-were-found-in-the-cluster/167466/5 "2019-03-15T16:59:56Z")

</div>

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