[
https://issues.apache.org/jira/browse/CASSANDRA-11989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15324754#comment-15324754
]
Tupshin Harper commented on CASSANDRA-11989:
--------------------------------------------
I'm envisioning that everything would be built off of low level "acquire_token"
and "release_token" type operations, and that giving nodes the ability to
dynamically perform those two operations safely will be a pre-requisite, so
would require a gossip enhancement. I'm avoiding depending on any more complex
semantics, and am working on mechanisms to to dynamically reallocate based on
just those two primitives.
> Rehabilitate Byte Ordered Partitioning
> --------------------------------------
>
> Key: CASSANDRA-11989
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11989
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Tupshin Harper
> Labels: ponies
> Fix For: 4.x
>
>
> This is a placeholder ticket to aid in NGCC discussion and should lead to a
> design doc.
> The general idea is that Byte Ordered Partitoning is the only way to maximize
> locality (beyond the healthy size of a single partition). Because of
> random/murmur's inability to do so, BOP has intrinsic value, assuming the
> operational downside are eliminated. This ticket tries to address the
> operational challenges of BOP and proposes that it should be the default in
> the distant future.
> http://slides.com/tupshinharper/rehabilitating_bop
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
