[
https://issues.apache.org/jira/browse/ACCUMULO-2901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14033470#comment-14033470
]
ASF subversion and git services commented on ACCUMULO-2901:
-----------------------------------------------------------
Commit 3ed4b2796ac95808af7aef62d93e6607cedc4d62 in accumulo's branch
refs/heads/master from [~elserj]
[ https://git-wip-us.apache.org/repos/asf?p=accumulo.git;h=3ed4b27 ]
ACCUMULO-2901 Document cases where replication won't work well
the architecture serves itself well for a certain set of problems, but is not a
universal
solution in its current implementation. provide a warning for some of those
edge cases to
manage user expectations and not mislead them.
> Document practical use-cases for replication
> --------------------------------------------
>
> Key: ACCUMULO-2901
> URL: https://issues.apache.org/jira/browse/ACCUMULO-2901
> Project: Accumulo
> Issue Type: Improvement
> Components: replication
> Reporter: Josh Elser
> Assignee: Josh Elser
> Fix For: 1.7.0
>
>
> Replication, while it is a cool feature, does have situations where it's not
> 100% foolproof and isn't guaranteed to provide eventual consistency given all
> situations.
> Document these cases, how they could be avoided with certain configuration,
> and any implications of those configurations.
> Short list
> * Failure on ACK from peer to primary could result in re-replication
> * Combiners might not be accurate
--
This message was sent by Atlassian JIRA
(v6.2#6252)
