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

Remove NOISY log from Mongo StreamAcknowledgementManager #5321

Merged
merged 1 commit into from
Jan 10, 2025

Conversation

dinujoh
Copy link
Member

@dinujoh dinujoh commented Jan 9, 2025

Description

Remove NOISY log from Mongo StreamAcknowledgementManager. We have metric to capture when this condition occurs, so removing logs as they are noisy

Check List

  • New functionality includes testing.
  • New functionality has a documentation issue. Please link to it in this PR.
    • New functionality has javadoc added
  • Commits are signed with a real name per the DCO

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Remove NOISY log from Mongo StreamAcknowledgementManager. We have metric to capture when this condition occurs, so removing logs as they are noisy

Signed-off-by: Dinu John <[email protected]>
Copy link

github-actions bot commented Jan 9, 2025

Unit Test Results

  2 822 files   -    227    2 822 suites   - 227   1h 7m 20s ⏱️ - 3m 22s
  9 977 tests  -      22    9 975 ✔️  -      22  1 💤 ±0  1 ±0 
24 909 runs   - 1 416  24 906 ✔️  - 1 416  1 💤  - 1  2 +1 

For more details on these failures, see this check.

Results for commit 38661b3. ± Comparison against base commit 2aa376e.

♻️ This comment has been updated with latest results.

@dlvenable dlvenable merged commit 3f7f5d2 into main Jan 10, 2025
46 of 52 checks passed
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.

2 participants