You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Ning Zhang (JIRA)" <ji...@apache.org> on 2011/03/01 06:17:37 UTC
[jira] Updated: (HIVE-2002) Expand exceptions caught for metastore
operations
[ https://issues.apache.org/jira/browse/HIVE-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ning Zhang updated HIVE-2002:
-----------------------------
Resolution: Fixed
Fix Version/s: 0.8.0
Status: Resolved (was: Patch Available)
Committed. Thanks Paul!
> Expand exceptions caught for metastore operations
> -------------------------------------------------
>
> Key: HIVE-2002
> URL: https://issues.apache.org/jira/browse/HIVE-2002
> Project: Hive
> Issue Type: Improvement
> Components: Metastore
> Affects Versions: 0.8.0
> Reporter: Paul Yang
> Assignee: Paul Yang
> Priority: Minor
> Fix For: 0.8.0
>
> Attachments: HIVE-2002.1.patch
>
>
> Currently, HiveMetaStore.executeWithRetry() catches two classes of exceptions and retries the metastore call when such exceptions occur. However, it does not catch some exceptions that could benefit from a retry:
> {code}
> Failed with exception javax.jdo.JDOException: Couldnt obtain a new sequence (unique id) : The MySQL server is running with the --read-only option so it cannot execute this statement
> NestedThrowables:
> java.sql.SQLException: The MySQL server is running with the --read-only option so it cannot execute this statement
> FAILED: Execution Error, return code 1 from org.apache.hadoop.hive.ql.exec.MoveTask
> {code}
> In this case, the MySQL server could be temporarily in a read-only mode, and a later DB call may succeed. To handle these situations, this JIRA proposes to expand the class of exceptions caught for retries.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira