accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (ACCUMULO-3530) alterTable/NamespaceProperty should use Fate locks
Date Mon, 26 Jan 2015 20:55:38 GMT

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

Christopher Tubbs edited comment on ACCUMULO-3530 at 1/26/15 8:55 PM:
----------------------------------------------------------------------

So, you just want to prevent properties, as viewed by the master, from being changed during
certain master operations?


was (Author: ctubbsii):
So, you just want to prevent properties, as viewed by the master, aren't changed during certain
master operations?

> 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)

Mime
View raw message