cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Masataka Yamaguchi (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-12279) nodetool repair hangs on non-existant table
Date Wed, 24 Aug 2016 08:42:20 GMT

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

Masataka Yamaguchi updated CASSANDRA-12279:
-------------------------------------------
    Attachment: new_result_example-v2.txt
                0001-CASSANDRA-12279-trunk-v2.patch
                0001-CASSANDRA-12279-2.2and3.0-v2.patch

Thank you for reviewing and testing.
I rewrote the patch for nodetool repair.
I added a new try-catch in RepairRunnable to catch the exception that happens when given keyspace
does not have at least one given table in getValidColumnFamilies.

I attached three files. First one is the patch for trunk, second one is the patch for 2.2
and 3.0 and third one is new output example.
Please review it if you have time.


> nodetool repair hangs on non-existant table
> -------------------------------------------
>
>                 Key: CASSANDRA-12279
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-12279
>             Project: Cassandra
>          Issue Type: Bug
>         Environment: Linux Ubuntu, Openjdk
>            Reporter: Benjamin Roth
>            Assignee: Masataka Yamaguchi
>            Priority: Minor
>              Labels: lhf
>         Attachments: 0001-CASSANDRA-12279-2.2.patch, 0001-CASSANDRA-12279-2.2and3.0-v2.patch,
0001-CASSANDRA-12279-3.0.patch, 0001-CASSANDRA-12279-trunk-v2.patch, 0001-CASSANDRA-12279-trunk.patch,
CASSANDRA-12279-trunk.patch, new_result_example-v2.txt, new_result_example.txt, org_result_example.txt
>
>
> If nodetool repair is called with a table that does not exist, ist hangs infinitely without
any error message or logs.
> E.g.
> nodetool repair foo bar
> Keyspace foo exists but table bar does not



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

Mime
View raw message