[
https://issues.apache.org/jira/browse/CASSANDRA-15812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17118597#comment-17118597
]
Sam Tunnicliffe edited comment on CASSANDRA-15812 at 5/28/20, 12:01 PM:
------------------------------------------------------------------------
bq. Is there a scenario in which using that behavior would be better?
I can't think of one. Given that this is only targetting a major release, maybe
we don't need to preserve the original behaviour. I'll push a patch to remove
it unless anyone has reservations. [~spod], [~jjirsa]?
was (Author: beobal):
> Is there a scenario in which using that behavior would be better?
I can't think of one. Given that this is only targetting a major release, maybe
we don't need to preserve the original behaviour. I'll push a patch to remove
it unless anyone has reservations. [~spod], [~jjirsa]?
> Submitting Validation requests can block ANTI_ENTROPY stage
> ------------------------------------------------------------
>
> Key: CASSANDRA-15812
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15812
> Project: Cassandra
> Issue Type: Bug
> Components: Consistency/Repair
> Reporter: Sam Tunnicliffe
> Assignee: Sam Tunnicliffe
> Priority: Normal
> Fix For: 4.0-alpha
>
>
> RepairMessages are handled on Stage.ANTI_ENTROPY, which has a thread pool
> with core/max capacity of one, ie. we can only process one message at a time.
>
> Scheduling validation compactions may however block the stage completely, by
> blocking on CompactionManager's ValidationExecutor while submitting a new
> validation compaction, in cases where there are already more validations
> running than can be executed in parallel.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
