You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Varun Gupta (JIRA)" <ji...@apache.org> on 2016/09/30 18:57:20 UTC

[jira] [Commented] (CASSANDRA-7545) Hints for a down node are written to a single partition in system.hints on the coordinator leading to contention

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

Varun Gupta commented on CASSANDRA-7545:
----------------------------------------

Is writing hints to flat file rather system.hints available on 2.2.X version. Or a patch which I can locally apply?

> Hints for a down node are written to a single partition in system.hints on the coordinator leading to contention
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-7545
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7545
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: graham sanderson
>
> The worst side effect is potentially orders of magnitude larger than suspected memory allocation due to a race condition updating the columns in the memtable (see CASSANDRA-7546)
> That said, having so many hints in a single partition has other negative side effects (non linear growth of sorted tree data structure overhead in memtable, just plain large number of tombstones in a row etc.)
> Ideally, the hints would be partitioned by both the nodeUUID, and a fixed number of (say 4) bits of a hash of the original rowmutation's partition key... even this small spreading of load has a significant improvement.



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