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 2014/07/21 16:30:39 UTC

[jira] [Commented] (ACCUMULO-1524) Abstract file pointers in metadata table

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

Keith Turner commented on ACCUMULO-1524:
----------------------------------------

Another problematic case users ran into is when a URI a user does not want to use is picked up from config.   After the user changes their config and restarts Accumulo, the URI may have been persisted to Accumulo metadata.  So making a mistake in configuring URIs can have a snowball effect.

> Abstract file pointers in metadata table
> ----------------------------------------
>
>                 Key: ACCUMULO-1524
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1524
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: tserver
>            Reporter: Christopher Tubbs
>            Priority: Minor
>
> ACCUMULO-118 interprets full URIs for file entries. It may be useful to instead to store a VolumeID + path, with a separate VolumeID -> URI mapping in configuration, for a level of indirection. This helps keep the METADATA from needing to be rewritten in strange cases, like moving a namenode from one host to another, or DNS name/IP address of namenode changes, or switching to a redundant fail-over DFS instance.



--
This message was sent by Atlassian JIRA
(v6.2#6252)