Skip to content

Conversation

vlofgren
Copy link
Contributor

The primary motivation for this is that in production, the large number of partitioned services has lead to an intermittent exhaustion of available database connections, as each service has a connection pool.

The decision to have a separate executor service dates back from when the index service was very slow to start, and the executor didn't always spin off its memory-hungry tasks into separate processes, which meant the executor would sometimes OOM and crash, and it was undesirable to bring the index down with it.

… the index service

The primary motivation for this is that in production, the large number of partitioned services has lead to an intermittent exhaustion of available database connections, as each service has a connection pool.

The decision to have a separate executor service dates back from when the index service was very slow to start, and the executor didn't always spin off its memory-hungry tasks into separate processes, which meant the executor would sometimes OOM and crash, and it was undesirable to bring the index down with it.
@vlofgren vlofgren force-pushed the deprecate-executor branch from fba213e to 62b696b Compare July 23, 2025 10:57
@vlofgren vlofgren changed the title Remove the separate executor service and roll it into the index service. Architecture: Remove the separate executor service and roll it into the index service. Jul 23, 2025
@vlofgren vlofgren linked an issue Jul 23, 2025 that may be closed by this pull request
@vlofgren vlofgren merged commit a43a177 into master Jul 23, 2025
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.

Merge execution functionality into index services
1 participant