[
https://issues.apache.org/jira/browse/CASSANDRA-11218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15615954#comment-15615954
]
Jeff Jirsa commented on CASSANDRA-11218:
----------------------------------------
Was chatting with [~beobal] on IRC briefly about starvation, and figured it's
worth mentioning here:
{quote}
09:52 <jeffj> also worth thinking about - within a type/level, is size the best
comparator? or hotness?
09:52 <jeffj> and if size, is largest first? or smallest first?
09:52 <jeffj> i'm not sure there's a universal right answer
{quote}
[~krummas] and [~kohlisankalp] - do you have thoughts on ordering compaction
tasks properly within a type? Is there something that's universally more likely
to be best for the user? Hotness? Size of sstables (sorted smallest to largest,
or largest to smallest)? As written, it's doing the largest transactions first
- do either of you have strong opinions that one specific approach is right or
wrong?
> Prioritize Secondary Index rebuild
> ----------------------------------
>
> Key: CASSANDRA-11218
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11218
> Project: Cassandra
> Issue Type: Improvement
> Components: Compaction
> 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.3.4#6332)
