With the changes introduced in https://github.com/rtoma/logspout-redis-logstash/commit/b96fbb63fa275395647ce01601f80d645227e591 we are seeing in production it is still possible for a pump send to timeout. The retry after a first error opens a connection again and tries to push again. If the first error is because of a timeout, there might not be enough time remaining out of the 1 second budget given by logspout. Fix ideas I have are introducing a timeout external from the redis client, simply removing the retry code, or fixing the 1 second timeout budget + closing the pump permanently after a single timeout upstream (I've opened an issue for this).
With the changes introduced in https://github.com/rtoma/logspout-redis-logstash/commit/b96fbb63fa275395647ce01601f80d645227e591 we are seeing in production it is still possible for a pump send to timeout. The retry after a first error opens a connection again and tries to push again. If the first error is because of a timeout, there might not be enough time remaining out of the 1 second budget given by logspout. Fix ideas I have are introducing a timeout external from the redis client, simply removing the retry code, or fixing the 1 second timeout budget + closing the pump permanently after a single timeout upstream (I've opened an issue for this).