cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benedict (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-9832) OpOrder: BarrierJumpingOp
Date Tue, 25 Aug 2015 09:46:46 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-9832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14711010#comment-14711010
] 

Benedict commented on CASSANDRA-9832:
-------------------------------------

[~beobal] would be best placed to discuss that. My understanding is that, originally, the
API could produce arbitrarily long operations. Now they are scoped to a single partition the
problem is no worse than in 2.1, I think, but this is still a problem, as large partitions
could lock up the node.

> OpOrder: BarrierJumpingOp
> -------------------------
>
>                 Key: CASSANDRA-9832
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9832
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Benedict
>            Assignee: Benedict
>            Priority: Minor
>             Fix For: 3.0 beta 2
>
>
> Necessary for safe secondary index operation under the new API: a long running operation
for use with OpOrder, that can jump between barriers at safe moments, without incurring the
cost of starting/stopping except when necessary.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message