Skip to content

Support asynchronous CommandStore message processing#27

Open
belliottsmith wants to merge 1 commit intoapache:trunkfrom
belliottsmith:rangetxns2
Open

Support asynchronous CommandStore message processing#27
belliottsmith wants to merge 1 commit intoapache:trunkfrom
belliottsmith:rangetxns2

Conversation

@belliottsmith
Copy link
Contributor

While messages are submitted to a CommandStore asynchronously, the processing of a message is then expected to be synchronous. However, it would be beneficial particularly for large range transactions, but also for recovery, to be able to defer some work that might involve IO to after the command store processing completes, e.g. for calculating dependencies.

…can be implemented by e.g. scanning sstables
@belliottsmith
Copy link
Contributor Author

ping

Copy link
Contributor

@aweisberg aweisberg left a comment

Choose a reason for hiding this comment

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

Can you rename zSlowSearcherandSlowSearchFunctionto something likeIncrementalSearcher` or whatever seems more descriptive and add a comment that the motivation is to allow implementations to process results without caching all of them or blocking for a long time or to avoid bringing them into the cache?

Otherwise yeah I am basically +1

@belliottsmith
Copy link
Contributor Author

Oh, somehow I missed you +1'd this. I'll rebase this perhaps onto bootstrap.

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.

2 participants