Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(export): add support in onGCE + no conn to metadata case #1021

Merged
merged 3 commits into from
Jun 12, 2024

Conversation

bwplotka
Copy link
Collaborator

@bwplotka bwplotka commented Jun 11, 2024

Fixes b/344740239 (edge case with GKE Metadata Server and GKE sandbox).

Regression test fails on prev flow (no context propagation)

image

Alternatives

Everything we do in FromFlags or constructor is within readines period. We
could consider moving potentially "slow" things on slow network or metadata srv
to exporter.Run. This could be questionable as for GMP to work
we at end need export functionality to work, so delaying that information or
making it surface in separation to readiness might not be helpful.

EDIT: Added PR against metadata so we can get rid of custom code in the future: googleapis/google-cloud-go#10370

@bwplotka bwplotka changed the title fix(export): make FromFlags & metadata call more reliable and observable fix(export): add support in onGCE + no conn to metadata case Jun 11, 2024
@bwplotka bwplotka marked this pull request as ready for review June 11, 2024 17:43
Fixes b/344740239 (edge case with GKE Metadata Server and GKE sandbox).

* Added debug logging.
* Updated metadata deps to get googleapis/google-cloud-go#9733 & use timeout-ed context
* Moved risky logic from FromFlags, see code comment why.
* Added regession test.

### Alternatives

Everything we do in FromFlags or constructor is within readines period. We
could consider moving potentially "slow" things on slow network or metadata srv
to exporter.Run. This could be questionable as for GMP to work
we at end need export functionality to work, so delaying that information or
making it surface in separation to readiness might not be helpful.

Signed-off-by: bwplotka <bwplotka@google.com>
Copy link
Member

@TheSpiritXIII TheSpiritXIII left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for the investigation and solid change!

func TestFromFlags_NotOnGCE(t *testing.T) {
// Asserting there is actually no GCE underneath.
if metadata.OnGCE() {
t.Fatal("This test assumes we don't run on GCP")
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggestion: t.Skip?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why? Do we expect to run in GCP? I don't think so, so let's fail fast (assert our assumption), WDYT? 🤔

// calls will timeout correctly (we propagate context properly).
func TestTryPopulateUnspecifiedFromMetadata(t *testing.T) {
// Asserting there is actually no GCE underneath.
if metadata.OnGCE() {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggestion: What if we just mock the metadata server? e.g. we create an interface and pass that to tryPopulateUnspecifiedFromMetadata?

Copy link
Collaborator Author

@bwplotka bwplotka Jun 12, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yea, what's the advantage of this versus what's now?

We can mock, but then we just test if we pass context correctly.

Here we test the metadata client to also pass context correctly through HTTP libs. I know we shouldn't generally test not our code.. but well, our product depends on this we just got regression because of that, thus let's maybe test this case?

// is not accessible on GCP, because it was disabled (404 errors), or not accessible
// (connection refused, slow network, e.g. sandbox + metadata disabled)
// it's a noop. Make sure to pass context with a timeout.
func tryPopulateUnspecifiedFromMetadata(ctx context.Context, logger log.Logger, opts *export.ExporterOpts) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggestion: Should we move this to a common utility, so we could reuse this for cmd/operator/main.go? Do we want to? We may suffer from the same problem there. In fact, we did see alerts based around the operator restarting too often at some point. May be the same or similar issue?

Copy link
Collaborator Author

@bwplotka bwplotka Jun 12, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good idea!

Doubt we are affected in the same way, but would be a good practice and little harm! I want to keep this PR small for bugfix though, let me check if this can be still "small" with operator changes.

Copy link
Collaborator Author

@bwplotka bwplotka Jun 12, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, I checked and indeed it would be nice, but I would postpone the operator (and rule-eval) changes until googleapis/google-cloud-go#10370 is merged (if anything). Will be easier. For now we could merge this and patch 0.12.0?

They are not directly affected to the known issue (you can't really move non collectors to sandbox nodes in GKE, for managed GMP)

bwplotka added a commit to bwplotka/google-cloud-go that referenced this pull request Jun 12, 2024
Hi!

The [GMP product got hit by the case](GoogleCloudPlatform/prometheus-engine#1021) where calls to metadata server
were hanging "forever" (GKE sandbox with disabled metadata server). Thanks to
recent work in this library, the clients support retry with backoff with timeouts.

However, still a single call was taking ~14s and since we made multiple of those, it took down
the service (readiness probe of 30s).

We can hackly workaround things (as we did in [here](GoogleCloudPlatform/prometheus-engine@e02408c)), by copying some code around, but I think the
above issue proves it would be helpful to actually add context to all metadata functions and methods.

I saw googleapis#9733 we started small, but
in this PR I actually spent 1h to add context to all things for consistency.

I self-reviewed carefuly, and tried to be consistent and extra safe, but careful
review is needed, given little testing.

Some minor extra changes (we can split to new commit/PR):
* Added comment around 14s worst case
* Added comment about OnGCE semantics which was a bit surprising for us.

Alternative would be something like

```
// WithContext sets the context that will be used for all client methods that
// does not support context. This means that e.g. the context passed in
// GetWithContext will override the context in WithContext
func (c *Client) WithContext(ctx context.Context) {
	c.ctx = ctx
}

```

.. but the logic is not trivial and we introdue some state to the global variable (defaultClient), which
can be source of problems if someone sets context for them, but another package in same binary resues it etc.

Given it's trivial to add (and use) new methods, I just did it.

Signed-off-by: bwplotka <bwplotka@gmail.com>
bwplotka added a commit to bwplotka/google-cloud-go that referenced this pull request Jun 12, 2024
Hi!

The [GMP product got hit by the case](GoogleCloudPlatform/prometheus-engine#1021) where calls to metadata server
were hanging "forever" (GKE sandbox with disabled metadata server). Thanks to
recent work in this library, the clients support retry with backoff with timeouts.

However, still a single call was taking ~14s and since we made multiple of those, it took down
the service (readiness probe of 30s).

We can hackly workaround things (as we did in [here](GoogleCloudPlatform/prometheus-engine@e02408c)), by copying some code around, but I think the
above issue proves it would be helpful to actually add context to all metadata functions and methods.

I saw googleapis#9733 we started small, but
in this PR I actually spent 1h to add context to all things for consistency.

I self-reviewed carefuly, and tried to be consistent and extra safe, but careful
review is needed, given little testing.

Some minor extra changes (we can split to new commit/PR):
* Added comment around 14s worst case
* Added comment about OnGCE semantics which was a bit surprising for us.
* When reviewing tests, I updated one test for best practices.

Alternative would be something like

```
// WithContext sets the context that will be used for all client methods that
// does not support context. This means that e.g. the context passed in
// GetWithContext will override the context in WithContext
func (c *Client) WithContext(ctx context.Context) {
	c.ctx = ctx
}

```

.. but the logic is not trivial and we introdue some state to the global variable (defaultClient), which
can be source of problems if someone sets context for them, but another package in same binary resues it etc.

Given it's trivial to add (and use) new methods, I just did it.

Signed-off-by: bwplotka <bwplotka@gmail.com>
Signed-off-by: bwplotka <bwplotka@google.com>
@bwplotka
Copy link
Collaborator Author

bwplotka commented Jun 12, 2024

I tested this PR on my repro cluster.

  • std node: works
  • sandbox node: works
  • no metadata node: works (we pass data via flags so it's fine)
  • sandbox, no metadata: collector runs, but export is unauth as expected

image

Metrics flow for 3 nodes as expected:

image

From this PR POV it's rdy to go I think

@bwplotka
Copy link
Collaborator Author

Copy link
Member

@TheSpiritXIII TheSpiritXIII left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm okay with all of your reasons. Thank you so much for the metadata library change! Much appreciated and great idea.

Signed-off-by: bwplotka <bwplotka@google.com>
@bwplotka
Copy link
Collaborator Author

🤗

@bwplotka bwplotka merged commit 054f28c into main Jun 12, 2024
27 checks passed
bwplotka added a commit that referenced this pull request Jun 12, 2024
bwplotka added a commit that referenced this pull request Jun 12, 2024
// be used as crucial labels for export to work against GCM's Prometheus target.
//
// Set a hard time limit due to readiness and liveliness probes during this stage.
mctx, cancel := context.WithTimeout(context.Background(), metadataFetchTimeout)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: should this have been ctx instead of context.Background()?

// of the metadata server. This is best-effort, so when the metadata server
// is not accessible on GCP, because it was disabled (404 errors), or not accessible
// (connection refused, slow network, e.g. sandbox + metadata disabled)
// it's a noop. Make sure to pass context with a timeout.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

suggestion: Could we add a TODO here referencing we can update/slim this code down once googleapis/google-cloud-go#10370 is merged?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants