[ https://issues.apache.org/jira/browse/HIVE-7167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14066963#comment-14066963 ]
Sergey Shelukhin commented on HIVE-7167: ---------------------------------------- Hmm, sure, +1. Sorry for long time taken, I was on vacation > Hive Metastore fails to start with SQLServerException > ----------------------------------------------------- > > Key: HIVE-7167 > URL: https://issues.apache.org/jira/browse/HIVE-7167 > Project: Hive > Issue Type: Bug > Components: Metastore > Affects Versions: 0.14.0 > Reporter: Xiaobing Zhou > Assignee: Xiaobing Zhou > Labels: patch,, test > Attachments: HIVE-7167.1.patch, HIVE-7167.2.patch > > > In the case that hiveserver2 uses embedded metastore and hiveserver uses > remote metastore, this exception comes up when hiveserver2 and hiveserver are > started simultaneously. > metastore service status is running but when I launch hive cli, I get > following metastore connection error: > C:\apps\dist\hive-0.13.0.2.1.2.0-1660\bin>hive.cmd > 14/05/09 17:40:03 WARN conf.HiveConf: DEPRECATED: hive.metastore.ds.retry.* > no l > onger has any effect. Use hive.hmshandler.retry.* instead > Logging initialized using configuration in > file:/C:/apps/dist/hive-0.13.0.2.1.2. > 0-1660/conf/hive-log4j.properties > Exception in thread "main" java.lang.RuntimeException: > java.lang.RuntimeExceptio > n: Unable to instantiate org.apache.hadoop.hive.metastore.HiveMetaStoreClient > at > org.apache.hadoop.hive.ql.session.SessionState.start(SessionState.jav > a:347) > at org.apache.hadoop.hive.cli.CliDriver.run(CliDriver.java:681) > at org.apache.hadoop.hive.cli.CliDriver.main(CliDriver.java:625) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. > java:57) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces > sorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.apache.hadoop.util.RunJar.main(RunJar.java:212) > Caused by: java.lang.RuntimeException: Unable to instantiate > org.apache.hadoop.h > ive.metastore.HiveMetaStoreClient > at > org.apache.hadoop.hive.metastore.MetaStoreUtils.newInstance(MetaStore > Utils.java:1413) > at > org.apache.hadoop.hive.metastore.RetryingMetaStoreClient.<init>(Retry > ingMetaStoreClient.java:62) > at > org.apache.hadoop.hive.metastore.RetryingMetaStoreClient.getProxy(Ret > ryingMetaStoreClient.java:72) > at > org.apache.hadoop.hive.ql.metadata.Hive.createMetaStoreClient(Hive.ja > va:2444) > at org.apache.hadoop.hive.ql.metadata.Hive.getMSC(Hive.java:2456) > at > org.apache.hadoop.hive.ql.session.SessionState.start(SessionState.jav > a:341) > ... 7 more > Caused by: java.lang.reflect.InvocationTargetException > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native > Method) > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstruct > orAccessorImpl.java:57) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingC > onstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:525) > at > org.apache.hadoop.hive.metastore.MetaStoreUtils.newInstance(MetaStore > Utils.java:1411) > ... 12 more > Caused by: MetaException(message:Could not connect to meta store using any of > th > e URIs provided. Most recent failure: > org.apache.thrift.transport.TTransportExce > ption: java.net.ConnectException: Connection refused: connect > at org.apache.thrift.transport.TSocket.open(TSocket.java:185) > at > org.apache.hadoop.hive.metastore.HiveMetaStoreClient.open(HiveMetaSto > reClient.java:336) > at > org.apache.hadoop.hive.metastore.HiveMetaStoreClient.<init>(HiveMetaS > toreClient.java:214) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native > Method) > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstruct > orAccessorImpl.java:57) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingC > onstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:525) > at > org.apache.hadoop.hive.metastore.MetaStoreUtils.newInstance(MetaStore > Utils.java:1411) > at > org.apache.hadoop.hive.metastore.RetryingMetaStoreClient.<init>(Retry > ingMetaStoreClient.java:62) > at > org.apache.hadoop.hive.metastore.RetryingMetaStoreClient.getProxy(Ret > ryingMetaStoreClient.java:72) > at > org.apache.hadoop.hive.ql.metadata.Hive.createMetaStoreClient(Hive.ja > va:2444) > at org.apache.hadoop.hive.ql.metadata.Hive.getMSC(Hive.java:2456) > at > org.apache.hadoop.hive.ql.session.SessionState.start(SessionState.jav > a:341) > at org.apache.hadoop.hive.cli.CliDriver.run(CliDriver.java:681) > at org.apache.hadoop.hive.cli.CliDriver.main(CliDriver.java:625) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. > java:57) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces > sorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.apache.hadoop.util.RunJar.main(RunJar.java:212) > Caused by: java.net.ConnectException: Connection refused: connect > at java.net.TwoStacksPlainSocketImpl.socketConnect(Native Method) > at > java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.ja > va:339) > at > java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocket > Impl.java:200) > at > java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java > :182) > at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:157) > at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:391) > at java.net.Socket.connect(Socket.java:579) > at org.apache.thrift.transport.TSocket.open(TSocket.java:180) > ... 19 more > ) > at > org.apache.hadoop.hive.metastore.HiveMetaStoreClient.open(HiveMetaSto > reClient.java:382) > at > org.apache.hadoop.hive.metastore.HiveMetaStoreClient.<init>(HiveMetaS > toreClient.java:214) > ... 17 more > Because of this issue, we are seeing many failures in hive related system > tests. -- This message was sent by Atlassian JIRA (v6.2#6252)