refactor: unify hummock+memory
with hummock+memory-shared
& fix compactor service in playground
#21847
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
Follow up of #21353.
This PR unifies
hummock+memory
withhummock+memory-shared
: we will always use the singleton in-memory object store in the process. This is because I cannot find an actual use case for differentiating them after removing the distributed in-memory e2e tests.This PR also fixes a bug that in
playground
(orsingle-node
with--in-memory
) mode, we specify the state store url as non-shared while still starting a compactor, which cannot access the objects as a result.Given that an embedded compactor will be started by the compute node service, there's no need to start a compactor service separately at all. Previously we will start 2 compactor service due to this reason. This PR fixes this as well.
risingwave/src/compute/src/server.rs
Lines 535 to 541 in 3c87f77
Checklist
Documentation
Release note