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

Nicholas Telford commented on CASSANDRA-2045:
---------------------------------------------

bq. if we're storing the full mutation, why add the complexity of hint headers 
and forwarding? Can we just make the coordinator responsible for all hints 
instead?
bq. So my point is that after we move away from storing hints as pointers to 
row data, there's no reason for the "prefer other replicas" optimization so we 
might as well just always store it on the coordinator.

While I agree with this, it seems that changing this is non-trivial (lots of 
changes to StorageProxy by the looks of it) so I'm leaning towards not 
including it in this ticket. It seems like an isolated idea though, albeit one 
that depends on this issue. Can we open this as a dependent ticket?

> Simplify HH to decrease read load when nodes come back
> ------------------------------------------------------
>
>                 Key: CASSANDRA-2045
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2045
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Chris Goffinet
>            Assignee: Nicholas Telford
>             Fix For: 1.0
>
>         Attachments: 
> 0001-Changed-storage-of-Hints-to-store-a-serialized-RowMu.patch, 
> 0002-Refactored-HintedHandoffManager.sendRow-to-reduce-co.patch, 
> 0003-Fixed-some-coding-style-issues.patch, 
> 0004-Fixed-direct-usage-of-Gossiper.getEndpointStateForEn.patch, 
> 0005-Removed-duplicate-failure-detection-conditionals.-It.patch, 
> 0006-Removed-handling-of-old-style-hints.patch, 2045-v3.txt, 
> CASSANDRA-2045-simplify-hinted-handoff-001.diff, 
> CASSANDRA-2045-simplify-hinted-handoff-002.diff
>
>
> Currently when HH is enabled, hints are stored, and when a node comes back, 
> we begin sending that node data. We do a lookup on the local node for the row 
> to send. To help reduce read load (if a node is offline for long period of 
> time) we should store the data we want forward the node locally instead. We 
> wouldn't have to do any lookups, just take byte[] and send to the destination.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to