accumulo-notifications mailing list archives

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


Keith Turner commented on ACCUMULO-3925:

What about [FateServiceHandler.waitForTableOperation()|]?
 I think it would get see a {{AcceptableFailureException}} which wraps a {{ThriftTableOperationException}}
and not handle that correctly.

Could have an interface instead of a class to avoid having to look at the cause.  Suppose
we created an interface called {{ExpectedException}} (note I used a different name based on
your javadoc for {{AcceptableFailureException}}, but I don't care what its named).  Could
do something like the following.

class ExpectedThriftTableOperationException extends ThriftTableOperationException implements
ExpectedException {
  public ExpectedThriftTableOperationException (ThriftTableOperationException e) {
    //clone expected exception

Then code that wanted to throw a quiet ThriftTableOperationException could do the following.

  try {
  } catch (ThriftTableOperationException e) {
    throw new ExpectedThriftTableOperationException(e);

> 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
>         Attachments: ACCUMULO-3925.patch
> {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