You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Mihai Suteu (JIRA)" <ji...@apache.org> on 2014/06/20 05:28:25 UTC
[jira] [Commented] (CASSANDRA-6719) redesign loadnewsstables
[ https://issues.apache.org/jira/browse/CASSANDRA-6719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14038321#comment-14038321 ]
Mihai Suteu commented on CASSANDRA-6719:
----------------------------------------
With the fix of the file naming conflicts in [CASSANDRA-6245 | https://issues.apache.org/jira/browse/CASSANDRA-6245] and [CASSANDRA-6514 | https://issues.apache.org/jira/browse/CASSANDRA-6514] is the parametrisation of nodetool refresh still a desired feature?
> redesign loadnewsstables
> ------------------------
>
> Key: CASSANDRA-6719
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6719
> Project: Cassandra
> Issue Type: New Feature
> Components: Tools
> Reporter: Jonathan Ellis
> Priority: Minor
> Labels: lhf
> Fix For: 3.0
>
>
> CFSMBean.loadNewSSTables scans data directories for new sstables dropped there by an external agent. This is dangerous because of possible filename conflicts with existing or newly generated sstables.
> Instead, we should support leaving the new sstables in a separate directory (specified by a parameter, or configured as a new location in yaml) and take care of renaming as necessary automagically.
--
This message was sent by Atlassian JIRA
(v6.2#6252)