accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Turner (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-3806) Failing to create a table/namespace because it already exists should not be a warning
Date Tue, 24 Jul 2018 14:06:00 GMT


Keith Turner commented on ACCUMULO-3806:

I have seen code where this is expected behavior.  Like launching lots of processes that all
attempt to create a table or an app that always attempts to create a table on startup.  If
ACCUMULO-3925 has not already handled this, I do not think it should create a warning.  The
client code calling create table gets an exception and it knows exactly what happened based
on the exception.

> Failing to create a table/namespace because it already exists should not be a warning
> -------------------------------------------------------------------------------------
>                 Key: ACCUMULO-3806
>                 URL:
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: fate
>            Reporter: Josh Elser
>            Priority: Major
>              Labels: newbie
>             Fix For: 2.0.0
>         Attachments: 0001-ACCUMULO-3806-changed-checkTableDoesNotExist-in-accu.patch
> This is a really common occurrence when you're running randomwalk:
> {noformat}
> Failed to execute Repo, tid=63d0421f1b17b04a
> 	ThriftTableOperationException(tableId:null, tableName:nspc_001.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}
> Concurrent table creations run: only one succeeds and the others fail. This is expected
and what FATE was designed to handle. We shouldn't be pushing these up to the monitor -- should
probably be a info or debug message.

This message was sent by Atlassian JIRA

View raw message