Repository navigation
bundle: add deployment history buffer telemetry - #7232
Draft
shreyas-goenka wants to merge 13 commits into
Draft
shreyas-goenka wants to merge 13 commits into
shreyas-goenka wants to merge 13 commits into
Conversation
Contributor
|
Commit: Regression test reportSelected 2 changed tests (limit=20, 0 not selected) 2 tests: regression=2 unreleased=0 coverage=0 failing=0
TestAccept/bundle/dms/multiple-resources/DMS=true: branch ✅ | main (e9687c1) ❌ | latest (v1.22.1) ❌main (e9687c1): latest (v1.22.1): TestAccept/bundle/dms/operation-upload-fails-once/DMS=true: branch ✅ | main (e9687c1) ❌ | latest (v1.22.1) ❌main (e9687c1): latest (v1.22.1): |
Collaborator
Integration test reportCommit: 7af90d6
Top 6 slowest tests (at least 2 minutes):
|
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Changes
Track deployment-history recording outcomes both per resource operation and per upload attempt.
Each buffered update contains its payload and an explicit pending/succeeded/failed state. The per-operation map points to the latest update. Workers update only the object they uploaded, so older completions cannot overwrite newer state. Intermediate recreation uploads do not finalize an operation. Aggregate
operation_recording_success_count,operation_recording_failure_count, andoperation_recording_pending_countpartition the total stagedstaged_operation_count. Missing staged operations are implicitly pending, so callers do not need to pass another list of keys.The existing
recording_attempt_success_countandrecording_attempt_failure_countstill count individual attempts directly at the call sites. Peak queue size and the timeout queue-length measurement are retained. Only aggregate counts are emitted.Matching ingestion schema: https://github.com/databricks-eng/universe/pull/2913283
Why
A single schema recreation can have one failed upload and one successful upload while its final history is successfully recorded. Report that as one recorded operation while retaining both attempt outcomes.
Tests
libs/dms,bundle/direct/dstate,bundle/phases, andlibs/telemetry/....Local checks used a temporary cached
golang.org/x/net v0.61.0override because the internal proxy blocks main'sv0.62.0as recently published. Tracked dependency files are unchanged.