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

Posted to notifications@accumulo.apache.org by "Christopher Tubbs (JIRA)" <ji...@apache.org> on 2015/01/26 18:09:34 UTC

[jira] [Commented] (ACCUMULO-3530) alterTable/NamespaceProperty should use Fate locks

    [ https://issues.apache.org/jira/browse/ACCUMULO-3530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14292093#comment-14292093 ] 

Christopher Tubbs commented on ACCUMULO-3530:
---------------------------------------------

How will this ensure consistency?

> alterTable/NamespaceProperty should use Fate locks
> --------------------------------------------------
>
>                 Key: ACCUMULO-3530
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3530
>             Project: Accumulo
>          Issue Type: Bug
>            Reporter: John Vines
>
> Fate operations, such as clone table, have logic in place to ensure consistency as the operation occurs. However, operaitons like alterTableProperty can still interfere because there is no locking done. We should add identical locking to these methods in MasterClientServiceHandler to help ensure consistency.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)