-
Notifications
You must be signed in to change notification settings - Fork 1.1k
LoggingHandler hangs the thread #2796
Copy link
Copy link
Closed
Labels
api: loggingIssues related to the Cloud Logging API.Issues related to the Cloud Logging API.type: feature request‘Nice-to-have’ improvement, new feature or different behavior or design.‘Nice-to-have’ improvement, new feature or different behavior or design.
Metadata
Metadata
Assignees
Labels
api: loggingIssues related to the Cloud Logging API.Issues related to the Cloud Logging API.type: feature request‘Nice-to-have’ improvement, new feature or different behavior or design.‘Nice-to-have’ improvement, new feature or different behavior or design.
Type
Fields
Give feedbackNo fields configured for issues without a type.
Our application is running on Google Kubernetes Engine using
gcr.io/google-appengine/jettyimage and usedcom.google.cloud.logging.LoggingHandlerto publish logs on Stackdriver. We noticed some worker threads becoming unresponsive over time. When the pod is shutting down we can see the following exception for each:We'll try to extract a thread dump to see why the future never completes, but the issue seems dangerous by itself:
LoggingImpl.java:543uses the non-timeout version ofFuture.get()which can cause any logger call to block the current thread forever unless interrupted. Would it be possible to use the timeout version with a reasonably big timeout, e.g. 60 seconds?