cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "T Jake Luciani (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-10230) Remove coordinator batchlog from materialized views
Date Tue, 24 Nov 2015 13:57:11 GMT


T Jake Luciani updated CASSANDRA-10230:
    Component/s: Coordination

> Remove coordinator batchlog from materialized views
> ---------------------------------------------------
>                 Key: CASSANDRA-10230
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Coordination
>            Reporter: T Jake Luciani
>            Assignee: T Jake Luciani
>             Fix For: 3.0.0 rc1
> We are considering removing or making optional the coordinator batchlog.  
> The batchlog primary serves as a way to quickly reach consistency between base and view
since we don't have any kind of read repair between base and view. But we do have repair so
as long as you don't lose nodes while writing at CL.ONE you will be eventually consistent.
> I've committed to the 3.0 branch a way to disable the coordinator with {{-Dcassandra.mv_disable_coordinator_batchlog=true}}
> The majority of the performance hit to throughput is currently the batchlog as shown
by this chart.
> I'd like to have tests run with and without this flag to validate how quickly we achieve
quorum consistency without repair writing with CL.ONE.   Once we can see there is little/no
impact we can permanently remove the coordinator batchlog.

This message was sent by Atlassian JIRA

View raw message