Error during global search: Search results from to of (NaN seconds)

Ameeth Paatil

unread,

Oct 8, 2018, 1:47:48 AM10/8/18

to Kylo Community

I am getting error (Search results from to of (NaN seconds)) while doing a global search below are my elastic search configurations. I have AWS elastic search version 5.5 tried version 6.3 as well but same error.

search.rest.host=<es_domain_name>
search.rest.port=80

# Elasticsearch server version (2 or 5)
search.rest.esversion=5

# This configuration should not require modification
#config.search.es.rest.url=http://${search.rest.host}
config.search.es.rest.url=http://${search.rest.host}:${search.rest.port}
config.search.engine=elasticsearch

Error Log:

2018-10-08 05:40:28 ERROR http-nio-8420-exec-6:ElasticSearchRestService:216 - An error occurred during submitting search request for query: {test}, start: {0}, size: {10}

org.elasticsearch.client.ResponseException: POST http://<es_domain_name>:80_search?ignore_unavailable=true&pretty=true: HTTP/1.1 400 Bad Request
<html>
<head><title>400 Bad Request</title></head>
<body bgcolor="white">
<center><h1>400 Bad Request</h1></center>
</body>
</html>

    at org.elasticsearch.client.RestClient$1.completed(RestClient.java:354)
    at org.elasticsearch.client.RestClient$1.completed(RestClient.java:343)
    at org.apache.http.concurrent.BasicFuture.completed(BasicFuture.java:119)
    at org.apache.http.impl.nio.client.DefaultClientExchangeHandlerImpl.responseCompleted(DefaultClientExchangeHandlerImpl.java:177)
    at org.apache.http.nio.protocol.HttpAsyncRequestExecutor.processResponse(HttpAsyncRequestExecutor.java:436)
    at org.apache.http.nio.protocol.HttpAsyncRequestExecutor.inputReady(HttpAsyncRequestExecutor.java:326)
    at org.apache.http.impl.nio.DefaultNHttpClientConnection.consumeInput(DefaultNHttpClientConnection.java:265)
    at org.apache.http.impl.nio.client.InternalIODispatch.onInputReady(InternalIODispatch.java:81)
    at org.apache.http.impl.nio.client.InternalIODispatch.onInputReady(InternalIODispatch.java:39)
    at org.apache.http.impl.nio.reactor.AbstractIODispatch.inputReady(AbstractIODispatch.java:114)
    at org.apache.http.impl.nio.reactor.BaseIOReactor.readable(BaseIOReactor.java:162)
    at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvent(AbstractIOReactor.java:337)
    at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvents(AbstractIOReactor.java:315)
    at org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:276)
    at org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:104)
    at org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:588)
    at java.lang.Thread.run(Thread.java:748)

2018-10-08 05:40:28 WARN http-nio-8420-exec-6:ElasticSearchRestService:188 - Search execution produced null response

Jagrut Sharma

unread,

Oct 8, 2018, 11:11:13 AM10/8/18

to Kylo Community

Hi Ameeth - ES's REST port is 9200 by default.

Thanks.

--

Jagrut

Ameeth Paatil

unread,

Oct 8, 2018, 12:47:39 PM10/8/18

to Kylo Community

AWS uses port 80 for elastic search instead of default 9200. I can try using 9200

Ameeth Paatil

unread,

Oct 9, 2018, 12:37:01 AM10/9/18

to Kylo Community

Hi Jagrut

With 9200 it gives the connection timeout

Caused by: org.apache.http.conn.HttpHostConnectException: Connect to <es_domain_name>:9200 [es_domain_name] failed: Connection timed out (Connection timed out)
    at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:151)
    at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:353)
    at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:380)
    at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:236)
    at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:184)
    at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:88)
    at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110)
    at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184)
    at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
    at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:107)
    at org.modeshape.jcr.index.elasticsearch.client.EsClient.indexExists(EsClient.java:64)
    at org.modeshape.jcr.index.elasticsearch.client.EsClient.createIndex(EsClient.java:81)
    at org.modeshape.jcr.index.elasticsearch.EsIndex.createIndex(EsIndex.java:92)
    ... 105 more

Jagrut Sharma

unread,

Oct 9, 2018, 12:29:39 PM10/9/18

to Kylo Community

Hi - The box running Kylo should have access to box running ES. Can you run this and check result?

$ curl <es_domain_name>:9200

--

Jagrut

Gregory Hart

unread,

Oct 9, 2018, 1:56:22 PM10/9/18

to Kylo Community

Hi Ameeth,

Could you also post the kylo-services.log file with this error message? It would help to get more context on this issue.

Ameeth Paatil

unread,

Oct 10, 2018, 8:04:54 AM10/10/18

to Kylo Community

Here is the curl output

[ec2-user@ip~]$ curl elasticsearch-devstack.net:9200

curl: (7) Failed to connect to elasticsearch-devstack.net port 9200: Connection timed out
[ec2-user@ip~]$
[ec2-user@ip~]$ curl elasticsearch-devstack.net:80
{
"name" : "X5S-Yy1",
"cluster_name" : "322663537532:devstack-es",
"cluster_uuid" : "SiNn8iVISSWn1n3hlG3aBQ",
"version" : {
    "number" : "6.3.1",
    "build_flavor" : "oss",
    "build_type" : "zip",
    "build_hash" : "e6df130",
    "build_date" : "2018-08-01T07:23:36.254471Z",
    "build_snapshot" : false,
    "lucene_version" : "7.3.1",
    "minimum_wire_compatibility_version" : "5.6.0",
    "minimum_index_compatibility_version" : "5.0.0"
},
"tagline" : "You Know, for Search"
}

And kylo-service.log are already posted just re-posting again

2018-10-10 11:54:26 ERROR http-nio-8420-exec-2:ElasticSearchRestService:216 - An error occurred during submitting search request for query: {interval}, start: {0}, size: {10}
org.elasticsearch.client.ResponseException: POST http://elasticsearch-devstack.net:80_search?ignore_unavailable=true&pretty=true: HTTP/1.1 400 Bad Request

<html>
<head><title>400 Bad Request</title></head>
<body bgcolor="white">
<center><h1>400 Bad Request</h1></center>
</body>
</html>

        at org.elasticsearch.client.RestClient$1.completed(RestClient.java:354)
        at org.elasticsearch.client.RestClient$1.completed(RestClient.java:343)
        at org.apache.http.concurrent.BasicFuture.completed(BasicFuture.java:119)
        at org.apache.http.impl.nio.client.DefaultClientExchangeHandlerImpl.responseCompleted(DefaultClientExchangeHandlerImpl.java:177)
        at org.apache.http.nio.protocol.HttpAsyncRequestExecutor.processResponse(HttpAsyncRequestExecutor.java:436)
        at org.apache.http.nio.protocol.HttpAsyncRequestExecutor.inputReady(HttpAsyncRequestExecutor.java:326)

at org.apache.http.impl.nio.client.InternalRequestExecutor.inputReady(InternalRequestExecutor.java:83)

        at org.apache.http.impl.nio.DefaultNHttpClientConnection.consumeInput(DefaultNHttpClientConnection.java:265)
        at org.apache.http.impl.nio.client.InternalIODispatch.onInputReady(InternalIODispatch.java:81)
        at org.apache.http.impl.nio.client.InternalIODispatch.onInputReady(InternalIODispatch.java:39)
        at org.apache.http.impl.nio.reactor.AbstractIODispatch.inputReady(AbstractIODispatch.java:114)
        at org.apache.http.impl.nio.reactor.BaseIOReactor.readable(BaseIOReactor.java:162)
        at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvent(AbstractIOReactor.java:337)
        at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvents(AbstractIOReactor.java:315)
        at org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:276)
        at org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:104)
        at org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:588)
        at java.lang.Thread.run(Thread.java:748)

2018-10-10 11:54:26 WARN http-nio-8420-exec-2:ElasticSearchRestService:188 - Search execution produced null response

Jagrut Sharma

unread,

Oct 10, 2018, 12:26:34 PM10/10/18

to Kylo Community

Hi Ameeth - Can you restart Kylo services and send the log?

Thanks.

--

Jagrut

Ameeth Paatil

unread,

Oct 11, 2018, 12:52:37 AM10/11/18

to Kylo Community

Please find attached kylo-service.log file

kylo-services.log

Gregory Hart

unread,

Oct 11, 2018, 2:27:51 PM10/11/18

to Kylo Community

Hi Ameeth,

Could you try changing config.search.es.rest.url to the below value?

http://${search.rest.host}:${search.rest.port}/

Gregory Hart

unread,

Oct 11, 2018, 2:30:08 PM10/11/18

to Kylo Community

Actually, that would only affect NiFi. This looks like a bug in Kylo. Could you create a JIRA issue for the Kylo team to investigate this issue?

https://kylo-io.atlassian.net/secure/Dashboard.jspa

If you need a fix for your current Kylo version then please contact Think Big Analytics for paid support.

Jagrut Sharma

unread,

Oct 11, 2018, 4:19:38 PM10/11/18

to Kylo Community

Hi Ameeth - The services log looks fine. We'll have to test Kylo with AWS Elasticsearch to see why the error is being thrown. As Greg said, can you please log a JIRA mentioning some details about how you spun up ES, so that we can try to replicate and fix the issue?

Thanks.

--

Jagrut

Ameeth Paatil

unread,

Oct 12, 2018, 1:43:26 AM10/12/18

to Kylo Community

Thanks for all the support. Created a ticket for this issue KYLO-2767

Reply all

Reply to author

Forward