Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Mon, 29 Jun 2015 20:18:04 +0000 (UTC)
From: "Josh Elser (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12841231.1435548202000.48993.1435609084760@Atlassian.JIRA>
In-Reply-To: <JIRA.12841231.1435548202000@Atlassian.JIRA>
References: <JIRA.12841231.1435548202000@Atlassian.JIRA>
 <JIRA.12841231.1435548202594@arcas>
Subject: [jira] [Updated] (ACCUMULO-3925) Remove unnecessary warning
 messages from FATE ops
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Josh Elser updated ACCUMULO-3925:
---------------------------------
    Attachment: ACCUMULO-3925.2.patch

Makes AcceptableException an interface in fate/ and makes an AcceptableThriftTableOperationException that the FATE ops throw. The Fate class can then key off of the AcceptableException class and choose the level to log at.

Better solution over the previous because the thrown AcceptableThriftTableOperationException is still a ThriftTableOperationException and requires less code elsewhere.

> Remove unnecessary warning messages from FATE ops
> -------------------------------------------------
>
>                 Key: ACCUMULO-3925
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3925
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: fate
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>            Priority: Minor
>             Fix For: 1.8.0
>
>         Attachments: ACCUMULO-3925.2.patch, ACCUMULO-3925.patch
>
>
> {noformat}
> Failed to execute Repo, tid=76367ba00e847e10
>     ThriftTableOperationException(tableId:null, tableName:ctt_000, op:CREATE, type:EXISTS, description:null)
>         at org.apache.accumulo.master.tableOps.Utils.checkTableDoesNotExist(Utils.java:54)
>         at org.apache.accumulo.master.tableOps.PopulateZookeeper.call(PopulateZookeeper.java:54)
>         at org.apache.accumulo.master.tableOps.PopulateZookeeper.call(PopulateZookeeper.java:30)
>         at org.apache.accumulo.master.tableOps.TraceRepo.call(TraceRepo.java:57)
>         at org.apache.accumulo.fate.Fate$TransactionRunner.run(Fate.java:72)
>         at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>         at org.apache.accumulo.fate.util.LoggingRunnable.run(LoggingRunnable.java:35)
>         at java.lang.Thread.run(Thread.java:745) 
> {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
(v6.3.4#6332)