HTTP/1.1 500 Server Error{"message":null}

Hi, I am encountering error from _bulk endpoint but I can't solve since the error message sent by ES is null. I am calling the _bulk endpoint via ES REST API.

Here is a snippet of the stacktrace I am getting:
HTTP/1.1 500 Server Error{"message":null} at org.elasticsearch.client.RestClient$1.completed( at org.elasticsearch.client.RestClient$1.completed( at org.apache.http.concurrent.BasicFuture.completed( at org.apache.http.impl.nio.client.DefaultClientExchangeHandlerImpl.responseCompleted( at org.apache.http.nio.protocol.HttpAsyncRequestExecutor.processResponse( at org.apache.http.nio.protocol.HttpAsyncRequestExecutor.inputReady( at org.apache.http.impl.nio.DefaultNHttpClientConnection.consumeInput( at org.apache.http.impl.nio.client.InternalIODispatch.onInputReady( at org.apache.http.impl.nio.client.InternalIODispatch.onInputReady( at org.apache.http.impl.nio.reactor.AbstractIODispatch.inputReady( at org.apache.http.impl.nio.reactor.BaseIOReactor.readable( at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvent( at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvents( at org.apache.http.impl.nio.reactor.AbstractIOReactor.execute( at org.apache.http.impl.nio.reactor.BaseIOReactor.execute( at org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$ at

Unfortunately, our elasticsearch server logs are not yet configured in AWS.

Thank you.

I'm afraid that we can't help without seeing elasticsearch logs.
What do you mean by not having setting the logs? Where/how are you running elasticsearch ?

Hi @dadoonet.
We're using Amazon Elasticsearch Service - our elasticsearch server logs is not yet configured to be published in Cloudwatch and we don't have any access to our elasticsearch settings in our prod environment.

I think this has something to do with a NullPointerException that's why the message is null. What do you think?
I've also searched in multiple sites but it seems that this particular issue is not discussed anywhere. Probably because most people have access to their elasticsearch server logs.

Thank you.

If you can share elasticsearch logs, you can hopefully help. May be ask AWS support otherwise?

BTW did you look at and ?

Cloud by elastic is one way to have access to all features, all managed by us. Think about what is there yet like Security, Monitoring, Reporting, SQL, Canvas, APM, Logs UI, Infra UI and what is coming next :slight_smile: ...

Thank you.
Would you know if there are issues in Elasticsearch that throws an NPE in bulk API?
I've read that there used to be some scenarios where NPE is thrown (e.g. no request body in a POST bulk API) but those causes that I've seen had been fixed in 5.4, if I'm not mistaken.
We're still on our way to upgrading our ES version but the version this particular issue occurs in is in 5.5.3.

I dunno without seeing the stacktrace which tells exactly where in the server code this is happening.

But for sure you should upgrade not only to a 5.5 version but at least to the latest 5.x.

Yes, our ES upgrade is on the way. Thank you, @dadoonet. I'll post again in this thread once I get more information from our elasticsearch logs.

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