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

Consolidate deployments #1508

Open
loewenheim opened this issue Aug 2, 2024 · 1 comment
Open

Consolidate deployments #1508

loewenheim opened this issue Aug 2, 2024 · 1 comment

Comments

@loewenheim
Copy link
Contributor

loewenheim commented Aug 2, 2024

We're currently deploying Symbolicator for 3 different enviroments (production, canary, LPQ) and 3 different platforms (native, JS, JVM). Since all combinations are possible, that results in 9 different deploys (with varying numbers of pods each). Ideally we would boil that down to just 2 (production and canary), i.e. no more LPQ and no more different platforms.

Some background: The LPQ machinery exists so we can move events that take a long time to process to a different queue so they don't block other more "well-behaved" events from being processed. It's effectiveness at this task is questionable, especially considering the massive complication it causes on the Sentry side. The problem may be better tackled by autoscaling.

The deployments for different platforms exist because the platforms get different amounts of load (JS the most, then native, then JVM) and also because when we were implementing the non-native platforms it was convenient to have separate instances that wouldn't take all symbolication down when we were tinkering with something. This might also be a matter of autoscaling.

@loewenheim
Copy link
Contributor Author

A significant part of this will happen via https://github.com/getsentry/team-ingest/issues/594.

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

No branches or pull requests

1 participant