ES May Permanently Block During Concurrent Query Operations #963
Comments
|
Hello! First of all this is not really the java client being used, it's the underlying low level rest client, but this shouldn't be happening anyways. I'm not too familiar with Kotlin so I can't understand if anything's wrong just by looking at the code. Would it be possible to have a small reproducer for the issue? |
Yes, I actually only used the ES package to construct the DSL, but the issue still occurred. This might be because the problem lies in the network layer API. The functionality of my Kotlin code above is similar to the Java code below: import org.apache.http.HttpHost;
import org.apache.http.entity.ContentType;
import org.apache.http.nio.entity.NStringEntity;
import org.apache.http.util.EntityUtils;
import org.elasticsearch.client.Request;
import org.elasticsearch.client.Response;
import org.elasticsearch.client.RestClient;
import org.elasticsearch.client.ResponseListener;
import com.alibaba.fastjson.JSON;
import java.util.concurrent.CompletableFuture;
public class ElasticsearchClient {
private static final RestClient client = createClient();
private static RestClient createClient() {
return RestClient.builder(HttpHost.create(LogScannerMain.main.pluginConfig.esHost))
.setCompressionEnabled(true)
.build();
}
public static CompletableFuture<EsResponse> postSearchAsync(SearchRequest request, String view) {
CompletableFuture<EsResponse> future = new CompletableFuture<>();
try {
Request esRequest = new Request("POST", "/" + view + "/_search");
FastJsonProvider jsonProvider = new FastJsonProvider();
FastJsonMapper mapper = new FastJsonMapper();
String jsonText;
try (FastJsonGenerator jsonGenerator = jsonProvider.createGenerator()) {
request.serialize(jsonGenerator, mapper);
jsonText = jsonGenerator.toString();
}
LogScannerMain.main.logger.trace("post search: " + jsonText);
esRequest.setEntity(new NStringEntity(jsonText, ContentType.APPLICATION_JSON));
client.performRequestAsync(esRequest, new ResponseListener() {
@Override
public void onSuccess(Response response) {
try {
String text = EntityUtils.toString(response.getEntity());
EsResponse esResponse = JSON.parseObject(text, EsResponse.class);
future.complete(esResponse);
} catch (Exception e) {
future.completeExceptionally(e);
}
}
@Override
public void onFailure(Exception exception) {
future.completeExceptionally(exception);
}
});
} catch (Exception e) {
future.completeExceptionally(e);
}
return future;
}
} |
|
Thank you! Will investigate ASAP |
|
Hey! I tried reproducing the issue using the provided java code, but on my machine everything works smoothly. The threads temporarily waiting for the Selector is normally okay, so let's see first if it could be something else: could you try executing the same code, without json deseralization, so just returning strings? I can see that |
Java API client version
8.17.0
Java version
21
Elasticsearch Version
8.10.2
Problem description
When I use concurrent requests to ES with the code below, the ES Java API may permanently block the current thread, eventually depleting my thread pool resources and causing my program to completely freeze.
My code is:
When ES blocks, the ES-related dump content obtained from jstack is as follows:
The text was updated successfully, but these errors were encountered: