Cant stream data from client node to ES after upgrade to 2.1


we are testing an upgrade to 2.1 and managed to successfully install ES 2.1 with kibana, all the plugins we use, and created a few mock indexes to store the data we receive from the client nodes (we use the same scripts as in 1.7.2 and the indexes were created successfully).
we are using ES bulk API for the inserts, but when redirecting the data stream to the new cluster it fails to insert the data.
the client nodes version is 1.7.2.

we get the following errors from client node log:
2016-01-05 01:12:33,022 worker #15} WARN org.elasticsearch.transport.netty:messageReceived():140 [XX_streamer] Message not fully read (response) for [254] handler$4@60e024ad, error [true], resetting
2016-01-05 01:12:33,024 worker #16} WARN [XX_streamer] failed to send ping to [[#zen_unicast_1#][][inet[]]]
org.elasticsearch.transport.RemoteTransportException: Failed to deserialize exception response from stream
Caused by: org.elasticsearch.transport.TransportSerializationException: Failed to deserialize exception response from stream
at org.elasticsearch.transport.netty.MessageChannelHandler.handlerResponseError(

bulk processor log:
2016-01-05 01:08:13,823 main INFO es_bulk_processor:connectClient():91 Trying to setup ES client
2016-01-05 01:08:47,605 main INFO es_bulk_processor:connectClient():105 Client connected
2016-01-05 01:08:47,606 main INFO es_bulk_processor:():63 Creating bulk processor
2016-01-05 01:09:48,421 tener][T#1] ERROR es_bulk_processor:afterBulk():79 Failure after bulk,executionId:1
org.elasticsearch.cluster.block.ClusterBlockException: blocked by: [SERVICE_UNAVAILABLE/1/state not recovered / initialized];[SERVICE_UNAVAILABLE/2/no master];
at org.elasticsearch.cluster.block.ClusterBlocks.globalBlockedException(
at org.elasticsearch.cluster.block.ClusterBlocks.globalBlockedRaiseException(
at org.elasticsearch.action.bulk.TransportBulkAction.executeBulk(
at org.elasticsearch.action.bulk.TransportBulkAction.access$000(
at org.elasticsearch.action.bulk.TransportBulkAction$1.onFailure(
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$ Source)
at Source)

no errors in ES logs.

so the first question, is it even possible to stream data from 1.7.2 client node to 2.1 ES cluster?
regarding the errors, it throws discovery errors event though i updated the unicast.hosts with the host and port of the client node, and the bulk log indicates that it connected to the cluster but cant insert.

any insight on the issues above would be welcome.


So the first question, is it even possible to stream data from 1.7.2 client node to 2.1 ES cluster?


OK then, i will upgrade the client nodes as well and test again.

thanks for the fast reply.

@dadoonet i have another question.

can 2.1 client node stream data to 1.7.2 cluster?
or both of them need to be upgraded together?


No it can't. 2.x can't speak with 1.x. And 1.x can't speak with 2.x.