hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Shelukhin (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-4897) Hive should handle AlreadyExists on retries when creating tables/partitions
Date Thu, 03 Mar 2016 00:03:18 GMT

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

Sergey Shelukhin commented on HIVE-4897:
----------------------------------------

I've seen this error fairly recently. It happens if the response was not delivered to client
due to a network problem (or theoretically due to timing issue with retry it can also happen,
if the retry is done after timeout but before the corresponding timeout on the server, and
the original request finishes before the retry is processed.
I've also seen it happen when the connection to underlying DB was lost in commitTxn, but the
commit still happened (that one time was due to BoneCP connection-closing bug, but it could
presumably also happen because of a connection issue). commitTxn fails, but the table is already
created. 

> Hive should handle AlreadyExists on retries when creating tables/partitions
> ---------------------------------------------------------------------------
>
>                 Key: HIVE-4897
>                 URL: https://issues.apache.org/jira/browse/HIVE-4897
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Sergey Shelukhin
>            Assignee: Aihua Xu
>         Attachments: HIVE-4897.patch, hive-snippet.log
>
>
> Creating new tables/partitions may fail with an AlreadyExistsException if there is an
error part way through the creation and the HMS tries again without properly cleaning up or
checking if this is a retry.
> While partitioning a new table via a script on distributed hive (MetaStore on the same
machine) there was a long timeout and then:
> {code}
> FAILED: Execution Error, return code 1 from org.apache.hadoop.hive.ql.exec.DDLTask. AlreadyExistsException(message:Partition
already exists:Partition( ...
> {code}
> I am assuming this is due to retry. Perhaps already-exists on retry could be handled
better.
> A similar error occurred while creating a table through Impala, which issued a single
createTable call that failed with an AlreadyExistsException. See the logs related to table
tmp_proc_8_d2b7b0f133be455ca95615818b8a5879_7 in the attached hive-snippet.log



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message