cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Shuler (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-13090) Coalescing strategy sleeps too much
Date Mon, 27 Feb 2017 16:20:45 GMT

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

Michael Shuler commented on CASSANDRA-13090:
--------------------------------------------

The CHANGE.txt entry for this ticket is under the incorrect releases in the cassandra-2.2,
cassandra-3.0, cassandra-3.11, and trunk branches. This was committed during release votes
were -tentative tagged.  The JIRA fix versions for 2.2.x and 3.0.x should be corrected, as
well, since this commit should be listed in CHANGES.txt under:
- 2.2.10 (currently under 2.2.9)
- 3.0.12 (currently under 3.0.11)
- 3.11.0 (currently under 3.10 in both cassandra-3.11 and trunk branches CHANGES.txt)

> Coalescing strategy sleeps too much
> -----------------------------------
>
>                 Key: CASSANDRA-13090
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13090
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Streaming and Messaging
>            Reporter: Corentin Chary
>            Assignee: Corentin Chary
>             Fix For: 2.2.9, 3.0.11, 3.11.0, 4.0
>
>         Attachments: 0001-Fix-wait-time-coalescing-CASSANDRA-13090-2.patch, 0001-Fix-wait-time-coalescing-CASSANDRA-13090.patch
>
>
> With the current code maybeSleep is called even if we managed to take maxItems out of
the backlog. In this case we should really avoid sleeping because it means that backlog is
building up.
> I'll send a patch shortly.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message