zane-neo

@model-collapse @ylwu-amzn @dhrubo-os @austintlee Please chime in.

A mistake here, async httpclient also has connection pools, the 100 is an example value.

# Benchmark results of replacing sync http-client to async ## Test settings ### commons settings - Benchmark doc count: 100k - One SageMaker endpoint with node type: ml.r5.4xlarge. This node...

@ylwu-amzn, fine tune the thread pool size definitely can improve the sync http client performance but this is not optimal, threads need system resources and also more threads will increase...

@reuschling Currently implementation doesn't allow empty string since empty string can produce embeddings successfully but it only consumes more disk space and doesn't provide any search relevance improvement. Instead `null`...

This doesn't looks like a bug, need @reuschling confirmation if the above response solved the issue.

Yes, will move this to neural-search.

> I do believe that OpenSearch nodes should be robust and handle failures gracefully. @peternied Agree on that but what I meant is a high level statistics, we usually measure...

> In case the target node is throwing these exceptions, it might just be so that they are removed from cluster as well. So, in that case simply retrying may...

It's fine to not add a new listener since using `new RetryableAction` is also an option to achieve the target of this issue, e.g. ``` public class MyTransportAction { @override...