[jira] [Resolved] (ACCUMULO-4793) Prioritize/Reprioritize bulk import requests

["Mark Owens (JIRA)" <ji...@apache.org>]

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

Mark Owens resolved ACCUMULO-4793.
----------------------------------
    Resolution: Won't Fix

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

> Prioritize/Reprioritize bulk import requests
> --------------------------------------------
>
>                 Key: ACCUMULO-4793
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-4793
>             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 capability would be the ability to prioritize and re-prioritize bulk import requests. Recent discussions with customers reveal this to be the highest priority on their feature request wish list.



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