You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Josh Elser (JIRA)" <ji...@apache.org> on 2014/12/02 16:34:12 UTC

[jira] [Resolved] (ACCUMULO-3377) BulkImporter.getAssignments provides unhelpful exception with bad file permissions

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

Josh Elser resolved ACCUMULO-3377.
----------------------------------
    Resolution: Fixed

Ok, thanks [~vines]. I'll close this since that's done.

> BulkImporter.getAssignments provides unhelpful exception with bad file permissions
> ----------------------------------------------------------------------------------
>
>                 Key: ACCUMULO-3377
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3377
>             Project: Accumulo
>          Issue Type: Bug
>          Components: tserver
>    Affects Versions: 1.6.0
>            Reporter: John Vines
>            Assignee: Josh Elser
>             Fix For: 1.6.2, 1.7.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> BulkImporter.getAssignments has the following code block
> {code}          try {
>             tabletsToAssignMapFileTo = findOverlappingTablets(ServerConfiguration.getSystemConfiguration(instance), fs, locator, mapFile, credentials);
>           } catch (Exception ex) {
>             log.warn("Unable to find tablets that overlap file " + mapFile.toString());
>           }
>           log.debug("Map file " + mapFile + " found to overlap " + tabletsToAssignMapFileTo.size() + " tablets");
> {code}
> In that call to find findOverlappingTablets, it is possible for an exception to occur that relates to an inability for the tserver to read the given file. Unfortunately, the exception isn't used in the log message and we provide no real feedback that the file cannot be read. We just fail it.
> I don't expect for us to magically recover, but we do need to log the exception as well to help make clear why this happened.



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