accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dave Marion (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-3006) Don't allow viewfs in instance.volumes
Date Tue, 22 Jul 2014 18:28:39 GMT


Dave Marion commented on ACCUMULO-3006:

Documenting what I understand after my discussion with [~ctubbsii] and [~kturner]. This may
break down into the following tickets:

1. Accumulo should only use the filesystems referenced in the instance.volumes property. With
the deprecation of instance.dfs.uri and instance.dfs.dir this property should become required
and we should not fall back to Hadoop's fs.defaultFS property value.

2. Accumulo should validate the configuration on init, init --add-volumes, and start. The
validation of other properties is out of scope of this issue, but if instance.volumes is either
a) not set, b) has no value, or c) resolves to some unknown filesystem scheme, then init and
init --add-volumes should fail quickly. There should be a whitelist of known good filesystem
schemes. If the filesystem schemes in instance.volumes are not on the whitelist, then either
start should fail or we should log warnings loudly. If we fail on start due to filesystem
scheme not being on the whitelist, then we also need to provide a way for users to ignore
the whitelist check knowingly.

> Don't allow viewfs in instance.volumes
> --------------------------------------
>                 Key: ACCUMULO-3006
>                 URL:
>             Project: Accumulo
>          Issue Type: Bug
>    Affects Versions: 1.6.0
>            Reporter: Dave Marion
>            Priority: Blocker
>             Fix For: 1.6.1, 1.7.0
> I think one of our folks put viewfs into instance.volumes on accident. File references
in accumulo.root and accumulo.metadata were then written with viewfs in the path. The garbage
collector then throws errors as compactions occur and it tries delete and move the files to
the hdfs users trash directory.
> viewfs should never be allowed in instance.volumes property. It should fail.

This message was sent by Atlassian JIRA

View raw message