Skip to content

Conversation

@eseliger
Copy link
Member

@eseliger eseliger commented May 12, 2025

Starting in Sourcegraph 6.4, the Symbols and Searcher services are now combined, for easier operation, simplified architecture, and better resource utilization.

Customers can delete the service if not deleted automatically, and may want to consider reallocating resources previously given to symbols to searcher. Environment variables should be copied over from symbols to searcher.

Test plan: This deployment ran for ~2 weeks on S2 and dotcom already and has signoff from team-product-platform.

Checklist

Starting in Sourcegraph 6.4, the Symbols and Searcher services are now combined, for easier operation, simplified architecture, and better resource utilization.

Customers can delete the service if not deleted automatically, and may want to consider reallocating resources previously given to symbols to searcher. Environment variables should be copied over from symbols to searcher.

Test plan: This deployment ran for ~2 weeks on S2 and dotcom already and has signoff from team-product-platform.
Copy link
Member Author

Choose a reason for hiding this comment

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

this was in the symbols dir previously, and the symbols file was in searcher 😆

Copy link
Contributor

Choose a reason for hiding this comment

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

😬

- ReadWriteOnce
resources:
requests:
storage: 50G
Copy link
Member Author

Choose a reason for hiding this comment

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

seems like this never requested a specific storage class -- weird but I don't really want to change this now and cause deployment issues, wdyt?

Copy link
Contributor

Choose a reason for hiding this comment

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

It's likely a mistake it never requested a storageClass to begin with 🙁
If we add it now though, K8s won't migrate the data (it won't delete it either), but the PVC would be recreated and be empty which would likely cause issue with our customers.

Copy link
Member Author

Choose a reason for hiding this comment

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

right, that's why I was hesitant to add it 🙈

@eseliger eseliger marked this pull request as ready for review May 12, 2025 13:43
@eseliger eseliger requested review from a team, ggilmore, pjlast and riazanovskiy May 12, 2025 13:44
@eseliger eseliger merged commit 1ac4f11 into main May 12, 2025
12 checks passed
@eseliger eseliger deleted the es/symbols-rm branch May 12, 2025 14:51
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

Successfully merging this pull request may close these issues.

3 participants