Skip to content
This repository has been archived by the owner on Oct 8, 2024. It is now read-only.

scaling-monolithic deployment mode #119

Closed
PietroPasotti opened this issue Jun 5, 2024 · 2 comments
Closed

scaling-monolithic deployment mode #119

PietroPasotti opened this issue Jun 5, 2024 · 2 comments

Comments

@PietroPasotti
Copy link
Contributor

Enhancement Proposal

It seems that with the 'all' target, you cannot scale tempo up.
Scaling to multiple units requires the 'scaling-monolithic' mode, which also means tempo requires the s3 integration.

https://grafana.com/docs/tempo/latest/setup/deployment/#scaling-monolithic-mode

proposal:
add a scaling:bool config option to tempo. If True, set the target to scaling-monolithic and set blocked until we have an s3 integration.

@PietroPasotti
Copy link
Contributor Author

counterproposal:

tempo-k8s can detect if it's scaled and if it has s3 configured.

if scaled and s3 configured: run all units with scaling-monolithic mode.
If scaled and s3 not ready: run leader with all, all other units go to blocked and alert of the missing s3 relation.

@mmkay
Copy link
Contributor

mmkay commented Jun 13, 2024

Completed in #127.

@mmkay mmkay closed this as completed Jun 13, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants