accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Owens (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-4793) Prioritize/Reprioritize bulk import requests
Date Thu, 01 Feb 2018 21:23:00 GMT


Mark Owens commented on ACCUMULO-4793:

It is a sub-task. 4793-4796 are sub-tasks of the overriding 4355 ticket. I broke out the four
individual requests into separate sub-task tickets. I copy and pasted much of the text from
4355 into each ticket for background.

> Prioritize/Reprioritize bulk import requests
> --------------------------------------------
>                 Key: ACCUMULO-4793
>                 URL:
>             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

View raw message