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 2016/05/27 00:18:13 UTC

[jira] [Commented] (ACCUMULO-4315) Log message during bulk import is misleading "Found candidate Volumes for Path but none of the Volumes are valid for the candidates [path]"

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

Christopher Tubbs commented on ACCUMULO-4315:
---------------------------------------------

We could lower it to trace... but we could also delete it. I'm not sure the message has any value whatsoever. All it's confirming is that you're bulk importing from a known filesystem (to avoid distcp when moving the file), but not a known directory. This is the expected case for bulk imports. I'm not sure if the code is exercised under any other circumstance where it'd be useful.

> Log message during bulk import is misleading "Found candidate Volumes for Path but none of the Volumes are valid for the candidates [path]"
> -------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: ACCUMULO-4315
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-4315
>             Project: Accumulo
>          Issue Type: Improvement
>    Affects Versions: 1.6.5, 1.7.1, 1.8.0
>            Reporter: Ed Coleman
>            Priority: Trivial
>             Fix For: 1.6.6, 1.7.3, 1.8.0
>
>
> During bulk ingest there are two debug level messages generated in the master debug log, one looks like a problem and then the next message indicates that the file was moved successfully to the target tablet directory. 
> The message in org.apache.accumulo.server.fs.VolumeManager is "Found candidate Volumes for Path but none of the Volumes are valid for the candidates [path]"
> This seems to occur because the directory of the "source" bulk ingest is not in the Accumulo instance.volume (on purpose) and is probably the general case for bulk ingest.
> The message could be reworded so that it does not appear that there is an issue with bulk ingest and depending where else the condition could occur, lower the level to trace if there are other messages more descriptive of operation that is potentially having the issue with file outside of the Accumulo instance volume.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)