You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@aurora.apache.org by "Mehrdad Nurolahzade (JIRA)" <ji...@apache.org> on 2017/02/03 16:46:51 UTC

[jira] [Updated] (AURORA-1866) Reduce Storage Write Lock Contention in RowGarbageCollector

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

Mehrdad Nurolahzade updated AURORA-1866:
----------------------------------------
    Priority: Major  (was: Minor)

> Reduce Storage Write Lock Contention in RowGarbageCollector
> -----------------------------------------------------------
>
>                 Key: AURORA-1866
>                 URL: https://issues.apache.org/jira/browse/AURORA-1866
>             Project: Aurora
>          Issue Type: Story
>          Components: Scheduler
>            Reporter: Mehrdad Nurolahzade
>
> {{RowGarbageCollector}} runs as a background service and deletes unreferenced rows in {{task_configs}} and {{job_keys}} tables (by default every two hours). This is achieved by deleting all existing rows (one by one) and silently ignoring the rows that fail deletion due to referential integrity constraints. The entire operation happens while holding the storage write lock. 
> We are not currently exposing stats on timing of this operation. There is a ticket to expose such stats ([AURORA-1842]). If proven to be an expensive operation, we need to consider batching the operations or setting a cap on the maximum number of rows garbage collected (and scheduling more frequently) to reduce contention on the storage write lock.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)