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

Delay telemetry object count #4361

Merged
merged 1 commit into from
Feb 29, 2024
Merged

Delay telemetry object count #4361

merged 1 commit into from
Feb 29, 2024

Conversation

parkerduckworth
Copy link
Member

What's being changed:

To avoid force loading a lazy-loaded shard for the sake of telemetry alone, the first telemetry payload (type INIT) will not contain the object count. Each following UPDATE or TERMINATE payload will contain the object count

Review checklist

  • Documentation has been updated, if necessary. Link to changed documentation:
  • Chaos pipeline run or not necessary. Link to pipeline:
  • All new code is covered by tests where it is reasonable.
  • Performance tests have been run or not necessary.

Copy link

sonarcloud bot commented Feb 29, 2024

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

@parkerduckworth parkerduckworth merged commit 655a1b7 into stable/v1.24 Feb 29, 2024
32 of 33 checks passed
@parkerduckworth parkerduckworth deleted the delay-telemetry branch February 29, 2024 21:11
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

2 participants