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.

Sign up for GitHub

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

Jump to bottom

Adjust SILO readiness endpoint #3840

Open
theosanderson opened this issue Mar 11, 2025 · 0 comments
Open

Adjust SILO readiness endpoint #3840

theosanderson opened this issue Mar 11, 2025 · 0 comments
Labels
high_priority Work on this as soon as possible (potentially post-MVP)

Comments

@theosanderson
Copy link
Member

Previously we had SILO and LAPIS in one deployment. That meant that until all of them were healthy we kept using the old SILO. Now we've split them out. Now SILO can become "healthy" and therefore receive traffic before it has finished SILO import. We should only make it ready after SILO import to avoid data downtime during deployments.
@theosanderson theosanderson added the high_priority Work on this as soon as possible (potentially post-MVP) label Mar 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
high_priority Work on this as soon as possible (potentially post-MVP)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@theosanderson