beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Luke Cwik (JIRA)" <>
Subject [jira] [Updated] (BEAM-2642) Upgrade to Google Auth 0.7.1
Date Mon, 24 Jul 2017 12:29:00 GMT


Luke Cwik updated BEAM-2642:
    Affects Version/s:     (was: 2.1.0)

> Upgrade to Google Auth 0.7.1
> ----------------------------
>                 Key: BEAM-2642
>                 URL:
>             Project: Beam
>          Issue Type: Bug
>          Components: sdk-java-gcp
>    Affects Versions: 2.0.0
>            Reporter: Luke Cwik
>            Assignee: Luke Cwik
>             Fix For: 2.1.0, 2.2.0
> Looking up application default credentials on a GCE VM can fail due to VM metadata server
being unavailable during VM launch. This is a rare event but Google Cloud Dataflow customers
hit this rare case one or two times a month due to the sheer number of VMs. GCE attempted
to mitigate VM metadata server unavailability but were only able to reduce it be an order
of magnitude thus we need support from the client to retry. Additionally, when contacting
the GCE VM metadata server, we should be using the fixed IP address avoiding the nameserver
lookup (another potential point of failure).
> Problem area in the code:
> Note that the code in this library and the Apiary auth support code are very similar.
The fix was done within the Apiary auth code (note the use of the static IP address and also
the presence of a fixed number of retries):
> It turned out that the fixes resulted in zero future customer contacts about this issue.
> Google Auth 0.7.1 was released containing these fixes mentioned in

This message was sent by Atlassian JIRA

View raw message