You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@kudu.apache.org by "Adar Dembo (JIRA)" <ji...@apache.org> on 2018/12/18 20:16:00 UTC

[jira] [Resolved] (KUDU-2289) Tablet deletion should be throttled

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

Adar Dembo resolved KUDU-2289.
------------------------------
       Resolution: Fixed
    Fix Version/s: 1.8.0

Yes, Will fixed this in commit 165688f83bbb00a41090e909ae4e17c463fa75e4.

> Tablet deletion should be throttled
> -----------------------------------
>
>                 Key: KUDU-2289
>                 URL: https://issues.apache.org/jira/browse/KUDU-2289
>             Project: Kudu
>          Issue Type: Improvement
>          Components: tserver
>            Reporter: Todd Lipcon
>            Assignee: Will Berkeley
>            Priority: Major
>             Fix For: 1.8.0
>
>
> Currently if a large amount of data is deleted simultaneously, the master will not do any throttling of the DeleteTablet requests send to the tservers. The tservers will use up to the configured number of service threads to work on deleting tablets. The deletion can be relatively heavy-weight -- lots of file system operations to hole-punch out the dead tablets, etc. This can have a negative impact on other concurrent workloads.
> It would be desirable to do some throttling either on the master or tserver side to avoid overwhelming disks and thread resources during heavy deletion.



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