Skip to content

Commit

Permalink
Internal: PlainTransportFuture should not set currentThread().interru…
Browse files Browse the repository at this point in the history
…pt()

We use PlainTransportFuture as a future for our transport calls. If someone blocks on it and it is interrupted, we throw an ElasticsearchIllegalStateException. We should not set  Thread.currentThread().interrupt(); in this case because we already communicate the interrupt through an exception.

Closes #9001
  • Loading branch information
bleskes committed Dec 18, 2014
1 parent 5e27885 commit 7f54170
Showing 1 changed file with 0 additions and 1 deletion.
Expand Up @@ -62,7 +62,6 @@ public V txGet(long timeout, TimeUnit unit) throws ElasticsearchException {
} catch (TimeoutException e) {
throw new ElasticsearchTimeoutException(e.getMessage());
} catch (InterruptedException e) {
Thread.currentThread().interrupt();
throw new ElasticsearchIllegalStateException("Future got interrupted", e);
} catch (ExecutionException e) {
if (e.getCause() instanceof ElasticsearchException) {
Expand Down

0 comments on commit 7f54170

Please sign in to comment.