[
https://issues.apache.org/jira/browse/CASSANDRA-11218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16111658#comment-16111658
]
Tania S Engel commented on CASSANDRA-11218:
-------------------------------------------
Could the index summary redistribution be the cause of the 29 minute gap in
stream time for this appliance? Typically in this test for us the Prepare
completed happens within the minute.
INFO [STREAM-INIT-/fd70:616e:6761:6561:ae1f:6bff:fe12:3de8:24642] 2017-07-28
*20:05*:28,929 StreamResultFuture.java:123 - [Stream
#1845aa20-73d0-11e7-8027-4139c6f86357, ID#0] Received streaming plan for
Bootstrap
INFO [IndexSummaryManager:1] 2017-07-28 20:13:06,822
IndexSummaryRedistribution.java:75 - Redistributing index summaries
INFO [STREAM-IN-/fd70:616e:6761:6561:ae1f:6bff:fe12:3de8:24642] 2017-07-28
*20:34*:10,712 StreamResultFuture.java:173 - [Stream
#1845aa20-73d0-11e7-8027-4139c6f86357 ID#0] Prepare completed. Receiving 0
files(0.000KiB), sending 57 files(369.250KiB)
> Prioritize Secondary Index rebuild
> ----------------------------------
>
> Key: CASSANDRA-11218
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11218
> Project: Cassandra
> Issue Type: Improvement
> Components: Compaction, Secondary Indexes
> Reporter: sankalp kohli
> Assignee: Jeff Jirsa
> Priority: Minor
>
> We have seen that secondary index rebuild get stuck behind other compaction
> during a bootstrap and other operations. This causes things to not finish. We
> should prioritize index rebuild via a separate thread pool or using a
> priority queue.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
