You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Alwyn Davis (JIRA)" <ji...@apache.org> on 2016/09/23 06:15:20 UTC

[jira] [Updated] (CASSANDRA-12695) Truncate ALWAYS not applied

     [ https://issues.apache.org/jira/browse/CASSANDRA-12695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alwyn Davis updated CASSANDRA-12695:
------------------------------------
    Attachment: 12695-trunk.patch

Small change to also truncate if multiple runs aren't going to occur and truncate is set to ALWAYS.

> Truncate ALWAYS not applied
> ---------------------------
>
>                 Key: CASSANDRA-12695
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-12695
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Alwyn Davis
>            Priority: Trivial
>              Labels: stress
>             Fix For: 3.x
>
>         Attachments: 12695-trunk.patch
>
>
> If truncate is set to ALWAYS and rate sets a specific thread count, the stress table is not actually truncated. E.g.
> {code}
> truncate=always -rate threads=4
> {code}
> This can cause an unexpected number of rows to be left in the table.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)