accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-3925) Remove unnecessary warning messages from FATE ops
Date Mon, 29 Jun 2015 15:43:05 GMT


Josh Elser commented on ACCUMULO-3925:

One interesting point about making this change is that we would need to only thrown a known-ignorable
exception from FATE op implementations because this log message is coming from the FATE framework

If we just wrap and consume the exceptions, it will change the semantics of the FATE op itself
which is a little scary.

> Remove unnecessary warning messages from FATE ops
> -------------------------------------------------
>                 Key: ACCUMULO-3925
>                 URL:
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: fate
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>            Priority: Minor
>             Fix For: 1.8.0
> {noformat}
> Failed to execute Repo, tid=76367ba00e847e10
>     ThriftTableOperationException(tableId:null, tableName:ctt_000, op:CREATE, type:EXISTS,
>         at org.apache.accumulo.master.tableOps.Utils.checkTableDoesNotExist(
>         at
>         at
>         at
>         at org.apache.accumulo.fate.Fate$
>         at java.util.concurrent.ThreadPoolExecutor.runWorker(
>         at java.util.concurrent.ThreadPoolExecutor$
>         at
>         at 
> {noformat}
> {noformat}
> Cannot move tables to a new namespace by renaming. The namespace for nspc_000.ctt_002
does not match ctt_001 
> {noformat}
> Lots of WARN messages seen during randomwalk that aren't system-level warning messages.
They are perfectly normal and expected. We should not be putting a warning to the monitor
for this messages. The exception thrown back to the client is sufficient.

This message was sent by Atlassian JIRA

View raw message