Large Trace Aggregation Exhausts Postgres Connections
- Dominant language
- Python
- Stars
- 44.8k
- Forks
- 4.9k
- Avg merge
- 21h 10m
- Merged PRs (30d)
- 635
Description
### Self-Hosted Version
25.7.0
### CPU Architecture
x86_64
### Docker Version
28.1.1
### Docker Compose Version
v2.35.1
### Machine Specification
- [x] My system meets the minimum system requirements of Sentry
### Steps to Reproduce
Use sentry on any browser/mobile client and API
### Expected Result
Standalone traces mobile -> API call, mobile -> api call
### Actual Result
A couple of hundred actions are aggregated under single trace which exhaust postgres connection and lock sentry till manual restart of containers
### Event ID
_No response_
### Additional info
#### API
SDK Name sentry.javascript.node
SDK Version 8.35.0
#### Mobile
sentry.javascript.react-native
6.16.0
Contributor guide
Research direction
Start by reproducing the report against self-hosted Sentry 25.7.0 using the listed JavaScript and React Native SDK versions, with browser or mobile clients calling an API. Investigate large trace aggregation and its PostgreSQL connection usage; done means the aggregation no longer exhausts connections or requires a manual container restart.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, postgresql, python, react-native
- Domain
- backend, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100