Skip to content

Allow configuration for maxOutstandingElementCount and limitExceededBehavior #953

@edudar

Description

@edudar

The current behavior is hardcoded as Block in GrpcLoggingRpc. This creates a problem, though. We run in a containerized environment with little overhead room for extra memory allocations. One of our services went down because Stackdriver was unavailable due to the 'quota exceeded' error, and log messages were piling up waiting to be sent. I'd sacrifice a few or a hundred log messages instead of a service. We use LoggingAppender with Logback. There seems to be no way to configure anything in the FlowControlSettings. I want to set a lower number for outstanding elements (like 1,000 instead of 100,000) and Ignore/ThrowException for limit behavior so that messages are discarded if they can't be delivered.

Metadata

Metadata

Assignees

Labels

🚨This issue needs some love.api: loggingIssues related to the googleapis/java-logging API.logging-resiliencepriority: p3Desirable enhancement or fix. May not be included in next release.type: questionRequest for information or clarification. Not an issue.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions