This appears to be new in 2.5, possibly due to this change in Elasticsearch which means that an exception is now thrown rather than just logging a warning. We should try setting spring.data.elasticsearch.client.reactive.socket-timeout to something larger than the 5 second default.