Pub/Sub c++ client: How to prevent/reduce ack failures on at least once delivery subscription

Client version: v2.39.0
MaxDeadline = seconds(0) (default value)
MaxDeadlineExtension = seconds(180)
MinDeadlineExtension = seconds(60)
MaxOutstandingMessages = 250
MaxConcurrency = 1

Time to time acks are failing. There is no retry for `at least once` delivery. How to reduce/prevent these failures? It happens 10-20 times a day.

Some of the logged errors [file_name] - [message]

> [NTPubSubLogger] /google-cloud-cpp/google/cloud/pubsub/internal/ack_handler_wrapper.cc:29 - error while trying to ack(), status=UNAVAILABLE: recvmsg:Connection reset by peer

> [NTPubSubLogger] /google-cloud-cpp/google/cloud/pubsub/internal/ack_handler_wrapper.cc:29 - error while trying to ack(), status=UNAVAILABLE: 502:Bad Gateway

It sounds like network issue but I doubt that. It happens every day 10-20 times. I can reproduce it with a 10 minutes of load tests by consuming/processing 300 messages per second.

Messages are ordered by account id in the system. When this happens the messages are stuck on pub/sub for 10-20 minutes because of unacked message. initial deadline=60 seconds, max deadline = 180 seconds. I observed the cpp client logs in debug mode. There is no ModifyAckDeadlineRequest is being made but still messages redelivered between 10-20 minutes later, in fact they should arrive in a few minutes. (That's another issue and maybe not related to the client.)

Comienza examinando google/cloud/pubsub/internal/ack_handler_wrapper.cc:29 y la configuración del cliente en el informe; después, reproduce los fallos con la prueba de carga descrita. Rastrea el comportamiento del acuse de recibo y de la extensión del deadline en torno a los errores UNAVAILABLE y a la redelivery. Se considera terminado cuando se haya identificado la causa de los fallos de ack y de la redelivery retrasada, y exista una forma verificada de reducirlos o prevenirlos.

Escrito por el modelo de indexación a partir del texto del issue.