cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Reddy (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-6719) redesign loadnewsstables
Date Fri, 20 May 2016 23:05:13 GMT

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

Mark Reddy commented on CASSANDRA-6719:
---------------------------------------

Hi [~yukim], I'd be interested in picking up this work. Here is a branch with my initial changes:
https://github.com/apache/cassandra/compare/trunk...markreddy:CASSANDRA-6719-load-new-sstables

I took a read through the ticket and I see your comment "For now, I want to keep current JXM
API and behavior as they are, but with warning message for your new API/behavior." Does this
mean you would like to have two loadNewSSTables methods exposed via StorageServiceMBean?

> 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.x
>
>         Attachments: 6719.patch
>
>
> 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.3.4#6332)

Mime
View raw message