You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Gopal V (JIRA)" <ji...@apache.org> on 2016/03/03 07:44:18 UTC
[jira] [Commented] (HIVE-13163) ORC MemoryManager thread checks are
fatal, should WARN
[ https://issues.apache.org/jira/browse/HIVE-13163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15177344#comment-15177344 ]
Gopal V commented on HIVE-13163:
--------------------------------
Test failures seem unrelated.
{code}
Caused by: MetaException(message:Unable to read from or write to hbase Failed 1 action: RetriesExhaustedException: 1 time, )
at org.apache.hadoop.hive.metastore.hbase.HBaseStore.createDatabase(HBaseStore.java:157)
at org.apache.hadoop.hive.metastore.HiveMetaStore$HMSHandler.createDefaultDB_core(HiveMetaStore.java:580)
at org.apache.hadoop.hive.metastore.HiveMetaStore$HMSHandler.createDefaultDB(HiveMetaStore.java:596)
at org.apache.hadoop.hive.metastore.HiveMetaStore$HMSHandler.init(HiveMetaStore.java:387)
at org.apache.hadoop.hive.metastore.HiveMetaStore$HMSHandler.<init>(HiveMetaStore.java:345)
at org.apache.hadoop.hive.metastore.HiveMetaStoreClient.<init>(HiveMetaStoreClient.java:222)
at org.apache.hadoop.hive.ql.metadata.SessionHiveMetaStoreClient.<init>(SessionHiveMetaStoreClient.java:68)
at org.apache.hadoop.hive.ql.metadata.Hive.createMetaStoreClient(Hive.java:3128)
at org.apache.hadoop.hive.ql.metadata.Hive.getMSC(Hive.java:3169)
at org.apache.hadoop.hive.ql.metadata.Hive.getMSC(Hive.java:3149)
at org.apache.hadoop.hive.ql.session.SessionState.start(SessionState.java:530)
... 28 more
{code}
> ORC MemoryManager thread checks are fatal, should WARN
> -------------------------------------------------------
>
> Key: HIVE-13163
> URL: https://issues.apache.org/jira/browse/HIVE-13163
> Project: Hive
> Issue Type: Bug
> Components: ORC
> Affects Versions: 2.0.0, 2.1.0
> Reporter: Gopal V
> Assignee: Gopal V
> Labels: PIG
> Attachments: HIVE-13163.1.patch
>
>
> The MemoryManager is tied to a WriterOptions on create, which can occur in a different thread from the writer calls.
> This is unexpected, but safe and needs a warning not a fatal.
> {code}
> /**
> * Light weight thread-safety check for multi-threaded access patterns
> */
> private void checkOwner() {
> Preconditions.checkArgument(ownerLock.isHeldByCurrentThread(),
> "Owner thread expected %s, got %s",
> ownerLock.getOwner(),
> Thread.currentThread());
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)