cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Yeschenko (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-9811) Tie counter shards' logical clock value to timestamps
Date Fri, 03 Jun 2016 21:46:59 GMT

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

Aleksey Yeschenko commented on CASSANDRA-9811:
----------------------------------------------

Committed as [ecaf3b079dad89e220885791fefb1372c3d2f9d6|https://github.com/apache/cassandra/commit/ecaf3b079dad89e220885791fefb1372c3d2f9d6]
to trunk.

> Tie counter shards' logical clock value to timestamps
> -----------------------------------------------------
>
>                 Key: CASSANDRA-9811
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9811
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Aleksey Yeschenko
>            Assignee: Aleksey Yeschenko
>            Priority: Minor
>             Fix For: 3.8
>
>
> CASSANDRA-6506 will get rid of counter shards, turning them into elements of a map. And
we'll be using the logical clock values as map element timestamps.
> To avoid unpleasant initial performance (being unable to perform certain sstable optimisations
on the read path), we should switch the shards to use {{max(timestamp, clock + 1)}} now, in
advance of CASSANDRA-6506 switch.



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

Mime
View raw message