New log effect type: log_ext
that allows entries residing in segment files to be read by another process.
#477
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.
Introduce a new version of the
log
effect (log_ext
) that allows any indexes referring to a command stored in a segment (rather than in the memtable) to be read by another process on the same node.Any indexes requested that are stored in the memtable are read by the ra server process but the remainder of entries are
provided as a "read plan" that another process could execute.
This feature is useful for offloading segment read work to RabbitMQ session/channel processes during consumption.