You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Christopher Tubbs (JIRA)" <ji...@apache.org> on 2019/04/23 23:25:00 UTC

[jira] [Resolved] (ACCUMULO-4795) cancel bulk import in progress

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

Christopher Tubbs resolved ACCUMULO-4795.
-----------------------------------------
    Resolution: Won't Fix

This only applies to the legacy bulk import, which has been superseded by the newer bulk import API.

> cancel bulk import in progress
> ------------------------------
>
>                 Key: ACCUMULO-4795
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-4795
>             Project: Accumulo
>          Issue Type: Sub-task
>          Components: master, tserver
>            Reporter: Mark Owens
>            Priority: Major
>
> Accumulo currently provides mechanisms to initiate bulk imports and to list bulk imports in progress. Scheduling of bulk import requests is not entirely deterministic, and most of the execution of a bulk-import request is done in a non-preemptable manner. As such, any bulk import which takes very long to complete can block bulk imports with higher operational priority for significant periods.
> To better support bulk-import-heavy applications, it would be nice if Accumulo would offer additional mechanisms for controlling the scheduling and execution of bulk imports
> One such feature would be the ability to cancel bulk import in progress.
> If possible, canceling a partially completed bulk import request should result in a rollback of changes. That is, a bulk import should either succeed or make no changes.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)