accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Vines (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-3377) BulkImporter.getAssignments provides unhelpful exception with bad file permissions
Date Tue, 02 Dec 2014 06:12:12 GMT

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

John Vines commented on ACCUMULO-3377:
--------------------------------------

Oh, this ticket was entirely about adding the stack trace to that log.warn. That is the first
necessary step to any sort of automated response - determine what we need to respond to. TBH,
I'm not 100% certain the file permissions were the reason for this exception, but it's the
best conclusion I got.

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

Mime
View raw message