[jira] [Updated] (CASSANDRA-4146) sstableloader should detect and report failures

["Brandon Williams (Updated) (JIRA)" <ji...@apache.org>]

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

Brandon Williams updated CASSANDRA-4146:
----------------------------------------

    Summary: sstableloader should detect and report failures  (was: Delete sstables on abnormal termination of sstableloader session)
    
> sstableloader should detect and report failures
> -----------------------------------------------
>
>                 Key: CASSANDRA-4146
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4146
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Tools
>    Affects Versions: 1.0.9
>            Reporter: Manish Zope
>            Priority: Minor
>              Labels: sstableloader, tools
>             Fix For: 1.1.1
>
>         Attachments: 4146.txt
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> There are three cases where we have observed the abnormal termination
> 1) In case of exception while loading.
> 2) User terminates the loading process.
> 3) If some node is down OR un-reachable then sstableloader get stucked.In this case user have to terminate the process in between.
> In case of abnormal termination, sstables (which are added in this session) remains as it is on the cluster.In case user starts the process all over again by fixing the exception, it results in duplication of the data till Major compaction is triggered.
> sstableloader can maintain the session while loading the sstables in cluster.So in case of abnormal termination sstableloader triggers the event that will delete the sstables loaded in that session.
> Also It would be great to have timeout in case of sstableloader.That can be kept configurable.
> So if sstableloader process got stucked for period longer than timeout, it can terminate itself.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira