Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Mon, 28 Jan 2013 22:19:13 +0000 (UTC)
From: "Aleksey Yeschenko (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12629594.1359411441964.203785.1359411553523@arcas>
In-Reply-To: <JIRA.12629594.1359411441964@arcas>
References: <JIRA.12629594.1359411441964@arcas>
Subject: [jira] [Created] (CASSANDRA-5193) Memtable flushwriter can pick a
 blacklisted directory
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Aleksey Yeschenko created CASSANDRA-5193:
--------------------------------------------

             Summary: Memtable flushwriter can pick a blacklisted directory
                 Key: CASSANDRA-5193
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5193
             Project: Cassandra
          Issue Type: Bug
    Affects Versions: 1.2.1
            Reporter: Aleksey Yeschenko
            Assignee: Aleksey Yeschenko
             Fix For: 1.2.2


The top-level data directory will be picked by DiskAwareRunnable (directory = Directories.getLocationCapableOfSize(writeSize)), and the top-level data directory itself might not be blacklisted (most likely won't be).

For the same reason we can't just add a blacklist-check in the middle of Directories#getLocationCapableOfSize - most often it's the sstable directory that gets blacklisted.

The issue seems to be caused by/related to CASSANDRA-4292, which was committed just two days prior 2116-2118 and undid some blacklist-aware directory-picking logic.

Anyway, DiskAwareRunnable should be altered to respect directory blacklist.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira