sink elasticsearch Service call failed. No retries or retries exhausted.

[Nobe-yt]

When using the sink of the vector to write data to es, a high load on one of the nodes in es caused the request to fail. The vector discarded the log, is there any way to prevent the log from being lost

LOG ：
2023-08-31T02:27:05.788372Z WARN sink{component_kind="sink" component_id=to_es7 component_type=elasticsearch component_name=to_es7}:request{request_id=9893}:http: vector::internal_events::http_client: HTTP error. error=error trying to connect: tcp connect error: Connection refused (os error 111) error_type="request_failed" stage="processing" internal_log_rate_limit=true
2023-08-31T02:27:05.788447Z WARN sink{component_kind="sink" component_id=to_es7 component_type=elasticsearch component_name=to_es7}:request{request_id=9893}: vector::sinks::util::retries: Retrying after error. error=Failed to make HTTP(S) request: error trying to connect: tcp connect error: Connection refused (os error 111) internal_log_rate_limit=true
2023-08-31T02:27:07.871497Z WARN sink{component_kind="sink" component_id=to_es7 component_type=elasticsearch component_name=to_es7}:request{request_id=9894}:http: vector::internal_events::http_client: Internal log [HTTP error.] is being suppressed to avoid flooding.
2023-08-31T02:27:07.871570Z WARN sink{component_kind="sink" component_id=to_es7 component_type=elasticsearch component_name=to_es7}:request{request_id=9894}: vector::sinks::util::retries: Internal log [Retrying after error.] is being suppressed to avoid flooding.
2023-08-31T03:06:02.326726Z ERROR sink{component_kind="sink" component_id=to_es7 component_type=elasticsearch component_name=to_es7}:request{request_id=10425}: vector::sinks::util::retries: Not retriable; dropping the request. reason="error type: es_rejected_execution_exception, reason: rejected execution of processing of [1933846][indices:data/write/bulk[s][p]]: request: BulkShardRequest [[logstash-nginx-access-orouter-2023.08.31.03][0]] containing [1000] requests, target allocation id: q9o1zf2zSCupQm-xobRdpg, primary term: 1 on EsThreadPoolExecutor[name = dx-elk17.dx/write, queue capacity = 1000, org.elasticsearch.common.util.concurrent.EsThreadPoolExecutor@131730c3[Running, pool size = 40, active threads = 40, queued tasks = 1050, completed tasks = 445142]]" internal_log_rate_limit=true
2023-08-31T03:06:02.326838Z ERROR sink{component_kind="sink" component_id=to_es7 component_type=elasticsearch component_name=to_es7}:request{request_id=10425}: vector_common::internal_event::service: Service call failed. No retries or retries exhausted. error=None request_id=10425 error_type="request_failed" stage="sending" internal_log_rate_limit=true
2023-08-31T03:06:02.326862Z ERROR sink{component_kind="sink" component_id=to_es7 component_type=elasticsearch component_name=to_es7}:request{request_id=10425}: vector_common::internal_event::component_events_dropped: Events dropped intentional=false count=1000 reason="Service call failed. No retries or retries exhausted." internal_log_rate_limit=true

[jszwedko]

Unfortunately not at the moment but improvements in this area are being tracked here: #10870 . The intention is to eventually to have Vector not drop events when encountering those sorts of errors.

[Nobe-yt]

Okay, I understand. Thank you for your reply