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

Posted to notifications@accumulo.apache.org by "Keith Turner (JIRA)" <ji...@apache.org> on 2017/02/07 16:48:41 UTC

[jira] [Resolved] (ACCUMULO-4574) Modify TableOperations online to check for table online before executing fate operation.

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

Keith Turner resolved ACCUMULO-4574.
------------------------------------
    Resolution: Fixed

I merged this to 2.0.0 also

> Modify TableOperations online to check for table online before executing fate operation.
> ----------------------------------------------------------------------------------------
>
>                 Key: ACCUMULO-4574
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-4574
>             Project: Accumulo
>          Issue Type: Improvement
>    Affects Versions: 1.7.2
>            Reporter: Ed Coleman
>            Assignee: Ed Coleman
>            Priority: Minor
>             Fix For: 1.7.3, 1.8.1, 2.0.0
>
>   Original Estimate: 24h
>          Time Spent: 9h 50m
>  Remaining Estimate: 14h 10m
>
> The table operations online operation executes as a fate operation. If a transaction lock for the table is currently held (say by table compactions) the online operation will block.
> This modification essentially changes the behavior of the online operation to a NOOP if the table is currently online. If the current table state is online, then the operation returns immediately without queuing a fate operation to set the online table to online. This eliminates the blocking behavior of the operation if the table is already online.



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