cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yuki Morishita (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-5503) Large Dataset with Secondary Index
Date Wed, 20 Nov 2013 21:56:35 GMT


Yuki Morishita commented on CASSANDRA-5503:

I think streaming failure in this case is due to FD terminated streaming session as node was
marked down, which is triggered by GC(note: we use 2x phi threshold).
This FD behavior is unchanged in streaming 2.0.

Secondary index building on receiving side is always done when all SSTables under a CF is
And source nodes of streaming should not be stressed by streaming itself.

> Large Dataset with Secondary Index
> ----------------------------------
>                 Key: CASSANDRA-5503
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Brooke Bryan
> We have a cluster with 1 CF, and 1 secondary index.  Currently, there are around 12 billion
keys across 10 nodes, and we need to grow the cluster to support new data.  (This is only
a small % of our total data atm) 
> The problem we are faced with, is when joining a new node, the system will often sit
there joining, and then fail a stream stage, failing the process.  This has been the result
of another node running a compaction and building up its heap too high, or other issues. 
However, I think this problem could be massively reduced, and make the join process more stable,
if the joining node pulled in all the data from the other nodes, and built up its secondary
indexes after the other nodes have done everything they need to for the node to complete its

This message was sent by Atlassian JIRA

View raw message