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 2019/03/16 18:03:00 UTC

[jira] [Resolved] (ACCUMULO-4862) Import Table command does not provide proper volumes to the PreferredVolumeChooser

     [ https://issues.apache.org/jira/browse/ACCUMULO-4862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Christopher Tubbs resolved ACCUMULO-4862.
-----------------------------------------
    Resolution: Duplicate

Closed as duplicate of https://github.com/apache/accumulo/issues/1041
We are no longer tracking new issues on JIRA. Please report them on GitHub in future. Thanks!

> Import Table command does not provide proper volumes to the PreferredVolumeChooser
> ----------------------------------------------------------------------------------
>
>                 Key: ACCUMULO-4862
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-4862
>             Project: Accumulo
>          Issue Type: Bug
>          Components: core
>            Reporter: Drew Farris
>            Assignee: Drew Farris
>            Priority: Minor
>
> The PopulateMetadataTable phase of the Import Table command obtains table directories (e.g: hdfs://volume-a/accumulo/tables, hdfs://volume-b/accumulo/tables) instead of volumes (e.g: hdfs://volume-a/accumulo,hdfs://volume-b/accumulo). These are passed into the volume chooser in getClonedTabletDir(..)
> The PreferredVolumeChooser compares these table directories with proper volumes configured in the table.custom.preferredVolumes property. The result is an empty set. An AccumuloException is thrown with the message "After filtering preferred volumes, there are no valid instance volumes" and this terminates the Import Table process.
>  
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)