accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Turner (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-1524) Abstract file pointers in metadata table
Date Mon, 21 Jul 2014 14:30:39 GMT

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

Mime
View raw message