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

feat(ingest): DLQ all non-retriable messages even if schema is valid #67200

Merged
merged 1 commit into from Mar 19, 2024

Conversation

lynnagara
Copy link
Member

Since ingest messages contain json bytes inside a msgpack payload the schema cannot be relied on to determine whether to DLQ, as the inner message can be invalid even if schema checking still passes. This now DLQs any exception that is not marked Retriable.

Since ingest messages contain json bytes inside a msgpack payload
the schema cannot be relied on to determine whether to DLQ, as the
inner message can be invalid even if schema checking still passes.
This now DLQs any exception that is not marked Retriable.
@lynnagara lynnagara requested review from untitaker and a team March 18, 2024 22:04
@lynnagara lynnagara requested a review from a team as a code owner March 18, 2024 22:04
@github-actions github-actions bot added the Scope: Backend Automatically applied to PRs that change backend components label Mar 18, 2024
@lynnagara lynnagara changed the title feat(ingest): DLQ all messages even if schema is valid feat(ingest): DLQ all non-retriable messages even if schema is valid Mar 18, 2024
Copy link

codecov bot commented Mar 18, 2024

Codecov Report

Attention: Patch coverage is 75.00000% with 2 lines in your changes are missing coverage. Please review.

Project coverage is 84.32%. Comparing base (d0740ed) to head (0273525).
Report is 6 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master   #67200      +/-   ##
==========================================
- Coverage   84.32%   84.32%   -0.01%     
==========================================
  Files        5306     5306              
  Lines      237129   237128       -1     
  Branches    41008    41008              
==========================================
- Hits       199957   199956       -1     
  Misses      36954    36954              
  Partials      218      218              
Files Coverage Δ
src/sentry/ingest/consumer/simple_event.py 88.57% <100.00%> (-1.43%) ⬇️
src/sentry/ingest/consumer/processors.py 87.67% <60.00%> (-1.07%) ⬇️

... and 4 files with indirect coverage changes

try:
cached_value = cache.get(deduplication_key)
except Exception as exc:
raise Retriable(exc)
Copy link
Member

Choose a reason for hiding this comment

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

There's additional calls to redis and celery below (event_processing_store.store(data), task.delay in submit_symbolicate). Should these also be marked as Retriable?

Copy link
Member Author

Choose a reason for hiding this comment

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

They should already be wrapped in Retriable -- did this in an earlier PR. Just spotted this one I forgot earlier.

@lynnagara lynnagara merged commit ce17387 into master Mar 19, 2024
50 of 51 checks passed
@lynnagara lynnagara deleted the dlq-even-if-schema-is-valid branch March 19, 2024 20:39
@github-actions github-actions bot locked and limited conversation to collaborators Apr 4, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Scope: Backend Automatically applied to PRs that change backend components
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants