[
https://issues.apache.org/jira/browse/CASSANDRA-16935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17425236#comment-17425236
]
Benedict Elliott Smith commented on CASSANDRA-16935:
----------------------------------------------------
It's never too late to bikeshed, but the "norrl" isn't about legacy/not, it's
about the lack of read/read linearizability. i.e.
nor(ead)r(ead)l(inearizability). Specifically this is whether or not we fix
CASSANDRA-12126.
When CEP-14 lands there will be a v2 introduced (and a v2_norrl)
Happy to bikeshed the names, but doubt there are _good_ options here.
> Use paxos_variant to specify Paxos behaviour
> --------------------------------------------
>
> Key: CASSANDRA-16935
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16935
> Project: Cassandra
> Issue Type: Improvement
> Components: Feature/Lightweight Transactions
> Reporter: Benedict Elliott Smith
> Priority: Normal
> Fix For: 4.x
>
>
> This patch introduces a config property for specifying the desired Paxos
> implementation and semantics. Initially, this will support only v1_norrl and
> v2, with “norrl” meaning “no read/read linearizability” i.e. supporting those
> use cases that need to restore prior performance, but only for read/read
> interactions.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
