-
Notifications
You must be signed in to change notification settings - Fork 202
Stackdriver Monitoring exporter recieves Goaway after running an hour #869
Comments
FWIW, it is not consistently starting to fail after a long period of time. It sometimes takes minutes to start seeing the exception. |
I've tried directly running the Stackdriver monitoring client (not the exporter) for ~1 hour, and I also saw this exception. After searching for some document on this, I think this is not an error. A quote from HTTP/2 specs (http://httpwg.org/specs/rfc7540.html#NO_ERROR):
|
Should we re-connect? Are data still uploaded? What is the impact? |
If there is no impact, is it expected to log it as a warning? I'd expect us to be more silent. |
I'm not 100% sure but I think gRPC will do the retry in this case (from googleapis/google-cloud-java#1579). @zhangkun83 could you confirm that? I assume this has no impact, and this is not a bug of exporter, so skip logging this kind of error makes sense to me. I'll post a PR to improve logging once this is confirmed. |
/cc @ejona86 |
@ejona86 ping on this. |
I don't understand the questions here. What do you mean by reconnect and retry? Is there a reason you think something is going wrong (as in, behaviorally you see something is broken)? Is the failing call a long-lived RPC?
|
I filed googleapis/google-cloud-java#2795 to GCP Java client for further investigation. |
Update: Stackdriver thinks this is related to googleapis/google-cloud-java#2066. |
googleapis/google-cloud-java#2066 is fixed. I have tried running the StackdriverStatsExporter recently and haven't seen this issue again. Closing for now, feel free to reopen if you saw this issue again. |
After an hour later I start a server that exports to Stackdriver Monitoring, the worker thread throws the following exception:
The text was updated successfully, but these errors were encountered: