Skip to content

Improved AAE fullsync integration/2.0 pull request#620

Merged
borshop merged 3 commits into
2.0from
feature/pipelined-aae-fullsync-2.0
Sep 22, 2014
Merged

Improved AAE fullsync integration/2.0 pull request#620
borshop merged 3 commits into
2.0from
feature/pipelined-aae-fullsync-2.0

Conversation

@jtuple
Copy link
Copy Markdown
Contributor

@jtuple jtuple commented Sep 22, 2014

This is a 2.0 backport/integration pull-request for pull-requests #616, #618, #619

Jon Meredith and others added 3 commits September 22, 2014 13:11
Although keylisting has a pool for issuing gets, both the
AAE and the Keylist strategies serialize writing objects
from the sink process.  This adds a pool with a default size
of 100 shared across all fullsync sinks that make the writes async.

No difference in safety properties, neither version checks
the response from the put FSM.
@jtuple
Copy link
Copy Markdown
Contributor Author

jtuple commented Sep 22, 2014

Sibling 2.0 rebased branches: basho/riak_core#629, basho/riak_kv#1026

borshop added a commit that referenced this pull request Sep 22, 2014
Improved AAE fullsync integration/2.0 pull request

Reviewed-by: jonmeredith
@jonmeredith
Copy link
Copy Markdown
Contributor

@borshop merge

Looked over the code one last time to check rebase was good.

@borshop borshop merged commit 916be13 into 2.0 Sep 22, 2014
@seancribbs seancribbs deleted the feature/pipelined-aae-fullsync-2.0 branch April 1, 2015 23:48
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