java.util.concurrent.ExecutionException

There are no available Samebug tips for this exception. Do you have an idea how to solve this issue? A short tip would help users who saw this issue last week.

  • I can enter all information about my cloud, and it tests ok and accepts it. When I go to launch a new slave though, I get the following snippet: Stack trace javax.servlet.ServletException: java.lang.RuntimeException: org.jclouds.compute.RunNodesException: error running 1 node group(jenkins-slave) location(regionOne) image(cdaa7dff-8bf6-4dc7-a84a-2802e23c0c94) size(1) options({loginPrivateKeyPresent=true, scriptPresent=true, userMetadata={Name=jenkins-slave}, userData=[B@4a0d6539}) Execution failures: 1) ExecutionException on jenkins-slave-b77: java.util.concurrent.ExecutionException: org.jclouds.http.HttpResponseException: command: POST http://130.20.232.220:8774/v2/84ad49ccecf2478b9317b332c1490bd4/servers HTTP/1.1 failed with response: HTTP/1.1 400 null; content: [{"badRequest": {"message": "Multiple possible networks found, use a Network ID to be more specific.", "code": 400}}] at com.google.common.util.concurrent.AbstractFuture$Sync.getValue(AbstractFuture.java:306) at com.google.common.util.concurrent.AbstractFuture$Sync.get(AbstractFuture.java:293) at com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:116) at org.jclouds.concurrent.FutureIterables$1.run(FutureIterables.java:125) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) Caused by: org.jclouds.http.HttpResponseException: command: POST http://130.20.232.220:8774/v2/84ad49ccecf2478b9317b332c1490bd4/servers HTTP/1.1 failed with response: HTTP/1.1 400 null; content: [{"badRequest": {"message": "Multiple possible networks found, use a Network ID to be more specific.", "code": 400}}] ... There seems to be no way to specify a network_id, which is important to our setup.
    via by Kevin Fox,
  • I can enter all information about my cloud, and it tests ok and accepts it. When I go to launch a new slave though, I get the following snippet: Stack trace javax.servlet.ServletException: java.lang.RuntimeException: org.jclouds.compute.RunNodesException: error running 1 node group(jenkins-slave) location(regionOne) image(cdaa7dff-8bf6-4dc7-a84a-2802e23c0c94) size(1) options({loginPrivateKeyPresent=true, scriptPresent=true, userMetadata={Name=jenkins-slave}, userData=[B@4a0d6539}) Execution failures: 1) ExecutionException on jenkins-slave-b77: java.util.concurrent.ExecutionException: org.jclouds.http.HttpResponseException: command: POST http://130.20.232.220:8774/v2/84ad49ccecf2478b9317b332c1490bd4/servers HTTP/1.1 failed with response: HTTP/1.1 400 null; content: [{"badRequest": {"message": "Multiple possible networks found, use a Network ID to be more specific.", "code": 400}}] at com.google.common.util.concurrent.AbstractFuture$Sync.getValue(AbstractFuture.java:306) at com.google.common.util.concurrent.AbstractFuture$Sync.get(AbstractFuture.java:293) at com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:116) at org.jclouds.concurrent.FutureIterables$1.run(FutureIterables.java:125) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) Caused by: org.jclouds.http.HttpResponseException: command: POST http://130.20.232.220:8774/v2/84ad49ccecf2478b9317b332c1490bd4/servers HTTP/1.1 failed with response: HTTP/1.1 400 null; content: [{"badRequest": {"message": "Multiple possible networks found, use a Network ID to be more specific.", "code": 400}}] ... There seems to be no way to specify a network_id, which is important to our setup.
    via by Kevin Fox,
  • I'm encountering a case where the failure of futures returned from {{Session.executeAsync}} is dramatically delayed (over one minute). It seems this is caused by {{cluster.manager.executor}} becoming very backlogged when my hosts enter SUSPECT state and connections are closed while there are many inflight requests: {noformat} DEBUG [2015-01-28 22:15:24,923] [Hashed wheel timer #1] Error querying /127.0.0.1:9042, trying next host (error is: com.datastax.driver.core.TransportException: [/127.0.0.1:9042] Connection has been closed) {noformat} If connection cannot be re-established easily, the executor becomes very backlogged. The problem appears to come from {{RequestHandler.retry}} using the executor to retry a request and {{DCAwareRoundRobinPolicy.waitOnReconnection}} executing on each suspected host: {noformat:title=Retry task causing TIMED_WAITING in cluster.manager.executor thread} "Cassandra Java Driver worker-0" nid=36 state=TIMED_WAITING - waiting on <0x1b072aaf> (a com.google.common.util.concurrent.ListenableFutureTask) - locked <0x1b072aaf> (a com.google.common.util.concurrent.ListenableFutureTask) at sun.misc.Unsafe.park(Native Method) at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:226) at java.util.concurrent.FutureTask.awaitDone(FutureTask.java:422) at java.util.concurrent.FutureTask.get(FutureTask.java:199) at com.datastax.driver.core.policies.DCAwareRoundRobinPolicy.waitOnReconnection(DCAwareRoundRobinPolicy.java:368) at com.datastax.driver.core.policies.DCAwareRoundRobinPolicy.access$100(DCAwareRoundRobinPolicy.java:56) at com.datastax.driver.core.policies.DCAwareRoundRobinPolicy$1.computeNext(DCAwareRoundRobinPolicy.java:310) at com.datastax.driver.core.policies.DCAwareRoundRobinPolicy$1.computeNext(DCAwareRoundRobinPolicy.java:279) at com.google.common.collect.AbstractIterator.tryToComputeNext(AbstractIterator.java:143) at com.google.common.collect.AbstractIterator.hasNext(AbstractIterator.java:138) at com.datastax.driver.core.policies.TokenAwarePolicy$1.computeNext(TokenAwarePolicy.java:157) at com.datastax.driver.core.policies.TokenAwarePolicy$1.computeNext(TokenAwarePolicy.java:142) at com.google.common.collect.AbstractIterator.tryToComputeNext(AbstractIterator.java:143) at com.google.common.collect.AbstractIterator.hasNext(AbstractIterator.java:138) at com.datastax.driver.core.RequestHandler.sendRequest(RequestHandler.java:102) at com.datastax.driver.core.RequestHandler$1.run(RequestHandler.java:179) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) - java.util.concurrent.ThreadPoolExecutor$Worker@e1e012a {noformat} {noformat:title=Example of future taking longer than a minute to complete} ERROR [2015-01-28 22:16:09,638] [Cassandra Java Driver worker-6] [Delete] Timed out request failed after 69495ms. java.util.concurrent.ExecutionException: com.datastax.driver.core.exceptions.NoHostAvailableException: All host(s) tried for query failed (tried: /127.0.0.2:9042 (com.datastax.driver.core.TransportException: [/127.0.0.2:9042] Connection has been closed)) at com.google.common.util.concurrent.AbstractFuture$Sync.getValue(AbstractFuture.java:306) at com.google.common.util.concurrent.AbstractFuture$Sync.get(AbstractFuture.java:293) at com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:116) ... at com.google.common.util.concurrent.MoreExecutors$SameThreadExecutorService.execute(MoreExecutors.java:293) at com.google.common.util.concurrent.ExecutionList$RunnableExecutorPair.execute(ExecutionList.java:150) at com.google.common.util.concurrent.ExecutionList.execute(ExecutionList.java:135) at com.google.common.util.concurrent.AbstractFuture.setException(AbstractFuture.java:203) at com.datastax.driver.core.DefaultResultSetFuture.onException(DefaultResultSetFuture.java:137) at com.datastax.driver.core.RequestHandler.setFinalException(RequestHandler.java:250) at com.datastax.driver.core.RequestHandler.sendRequest(RequestHandler.java:108) at com.datastax.driver.core.RequestHandler$1.run(RequestHandler.java:179) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) Caused by: com.datastax.driver.core.exceptions.NoHostAvailableException: All host(s) tried for query failed (tried: /127.0.0.2:9042 (com.datastax.driver.core.TransportException: [/127.0.0.2:9042] Connection has been closed)) ... 5 more {noformat} The intent of the executor is for processing non-blocking tasks, but this particular task can become blocking if the host is in a suspected state (and also depending on the implementation of the used LBP), therefore I think we should move this task (the work in {{RequestHandler.retry}}) to a different executor as this could cause delay of important work, like triggering up and down events. It is probably ok to delay setting an exception on the Future compared to other important work that uses the executor. I should note that as soon as I had a non-suspected host, these tasks completed quickly. Example showing backlogged executor: !executor_backlogged.png|thumbnail! The test scenario used to reproduce this: # Configure read timeout of 500ms, connection timeout of 100ms. # Send continual queries (reads, selects, deletes, writes, etc. - sent up to 2400 simultaneous requests on 3 local nodes) # Execute script that does {{kill -STOP <pid>}} and then {{kill -CONT <pid>}} repeatedly on cassandra nodes. ([^suspend_nodes.sh]) As it takes a non-ideal scenario to create this, though I suppose it is theoretically possible for this to happen without these parameters (many inflight requests while a connection is closing and all hosts are suspected), so the severity may be lower than 'Major'.
    via by Andy Tolbert,
  • I'm encountering a case where the failure of futures returned from {{Session.executeAsync}} is dramatically delayed (over one minute). It seems this is caused by {{cluster.manager.executor}} becoming very backlogged when my hosts enter SUSPECT state and connections are closed while there are many inflight requests: {noformat} DEBUG [2015-01-28 22:15:24,923] [Hashed wheel timer #1] Error querying /127.0.0.1:9042, trying next host (error is: com.datastax.driver.core.TransportException: [/127.0.0.1:9042] Connection has been closed) {noformat} If connection cannot be re-established easily, the executor becomes very backlogged. The problem appears to come from {{RequestHandler.retry}} using the executor to retry a request and {{DCAwareRoundRobinPolicy.waitOnReconnection}} executing on each suspected host: {noformat:title=Retry task causing TIMED_WAITING in cluster.manager.executor thread} "Cassandra Java Driver worker-0" nid=36 state=TIMED_WAITING - waiting on <0x1b072aaf> (a com.google.common.util.concurrent.ListenableFutureTask) - locked <0x1b072aaf> (a com.google.common.util.concurrent.ListenableFutureTask) at sun.misc.Unsafe.park(Native Method) at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:226) at java.util.concurrent.FutureTask.awaitDone(FutureTask.java:422) at java.util.concurrent.FutureTask.get(FutureTask.java:199) at com.datastax.driver.core.policies.DCAwareRoundRobinPolicy.waitOnReconnection(DCAwareRoundRobinPolicy.java:368) at com.datastax.driver.core.policies.DCAwareRoundRobinPolicy.access$100(DCAwareRoundRobinPolicy.java:56) at com.datastax.driver.core.policies.DCAwareRoundRobinPolicy$1.computeNext(DCAwareRoundRobinPolicy.java:310) at com.datastax.driver.core.policies.DCAwareRoundRobinPolicy$1.computeNext(DCAwareRoundRobinPolicy.java:279) at com.google.common.collect.AbstractIterator.tryToComputeNext(AbstractIterator.java:143) at com.google.common.collect.AbstractIterator.hasNext(AbstractIterator.java:138) at com.datastax.driver.core.policies.TokenAwarePolicy$1.computeNext(TokenAwarePolicy.java:157) at com.datastax.driver.core.policies.TokenAwarePolicy$1.computeNext(TokenAwarePolicy.java:142) at com.google.common.collect.AbstractIterator.tryToComputeNext(AbstractIterator.java:143) at com.google.common.collect.AbstractIterator.hasNext(AbstractIterator.java:138) at com.datastax.driver.core.RequestHandler.sendRequest(RequestHandler.java:102) at com.datastax.driver.core.RequestHandler$1.run(RequestHandler.java:179) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) - java.util.concurrent.ThreadPoolExecutor$Worker@e1e012a {noformat} {noformat:title=Example of future taking longer than a minute to complete} ERROR [2015-01-28 22:16:09,638] [Cassandra Java Driver worker-6] [Delete] Timed out request failed after 69495ms. java.util.concurrent.ExecutionException: com.datastax.driver.core.exceptions.NoHostAvailableException: All host(s) tried for query failed (tried: /127.0.0.2:9042 (com.datastax.driver.core.TransportException: [/127.0.0.2:9042] Connection has been closed)) at com.google.common.util.concurrent.AbstractFuture$Sync.getValue(AbstractFuture.java:306) at com.google.common.util.concurrent.AbstractFuture$Sync.get(AbstractFuture.java:293) at com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:116) ... at com.google.common.util.concurrent.MoreExecutors$SameThreadExecutorService.execute(MoreExecutors.java:293) at com.google.common.util.concurrent.ExecutionList$RunnableExecutorPair.execute(ExecutionList.java:150) at com.google.common.util.concurrent.ExecutionList.execute(ExecutionList.java:135) at com.google.common.util.concurrent.AbstractFuture.setException(AbstractFuture.java:203) at com.datastax.driver.core.DefaultResultSetFuture.onException(DefaultResultSetFuture.java:137) at com.datastax.driver.core.RequestHandler.setFinalException(RequestHandler.java:250) at com.datastax.driver.core.RequestHandler.sendRequest(RequestHandler.java:108) at com.datastax.driver.core.RequestHandler$1.run(RequestHandler.java:179) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) Caused by: com.datastax.driver.core.exceptions.NoHostAvailableException: All host(s) tried for query failed (tried: /127.0.0.2:9042 (com.datastax.driver.core.TransportException: [/127.0.0.2:9042] Connection has been closed)) ... 5 more {noformat} The intent of the executor is for processing non-blocking tasks, but this particular task can become blocking if the host is in a suspected state (and also depending on the implementation of the used LBP), therefore I think we should move this task (the work in {{RequestHandler.retry}}) to a different executor as this could cause delay of important work, like triggering up and down events. It is probably ok to delay setting an exception on the Future compared to other important work that uses the executor. I should note that as soon as I had a non-suspected host, these tasks completed quickly. Example showing backlogged executor: !executor_backlogged.png|thumbnail! The test scenario used to reproduce this: # Configure read timeout of 500ms, connection timeout of 100ms. # Send continual queries (reads, selects, deletes, writes, etc. - sent up to 2400 simultaneous requests on 3 local nodes) # Execute script that does {{kill -STOP <pid>}} and then {{kill -CONT <pid>}} repeatedly on cassandra nodes. ([^suspend_nodes.sh]) As it takes a non-ideal scenario to create this, though I suppose it is theoretically possible for this to happen without these parameters (many inflight requests while a connection is closing and all hosts are suspected), so the severity may be lower than 'Major'.
    via by Andy Tolbert,
  • Explore service does not start in this environment, due to which /system/services returns NOTOK for explore, so integration tests do not even start. when I run the hive command, it throws the following exceptions: {code} $ hive version Logging initialized using configuration in jar:file:/usr/lib/hive/lib/hive-common-0.13.1-cdh5.2.6.jar!/hive-log4j.properties Exception in thread "main" java.lang.RuntimeException: java.lang.RuntimeException: Unable to instantiate org.apache.hadoop.hive.metastore.HiveMetaStoreClient at org.apache.hadoop.hive.ql.session.SessionState.start(SessionState.java:347) at org.apache.hadoop.hive.cli.CliDriver.run(CliDriver.java:689) at org.apache.hadoop.hive.cli.CliDriver.main(CliDriver.java:633) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.apache.hadoop.util.RunJar.main(RunJar.java:212) Caused by: java.lang.RuntimeException: Unable to instantiate org.apache.hadoop.hive.metastore.HiveMetaStoreClient at org.apache.hadoop.hive.metastore.MetaStoreUtils.newInstance(MetaStoreUtils.java:1426) at org.apache.hadoop.hive.metastore.RetryingMetaStoreClient.<init>(RetryingMetaStoreClient.java:63) at org.apache.hadoop.hive.metastore.RetryingMetaStoreClient.getProxy(RetryingMetaStoreClient.java:73) at org.apache.hadoop.hive.ql.metadata.Hive.createMetaStoreClient(Hive.java:2462) at org.apache.hadoop.hive.ql.metadata.Hive.getMSC(Hive.java:2481) at org.apache.hadoop.hive.ql.session.SessionState.start(SessionState.java:341) ... 7 more Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:526) at org.apache.hadoop.hive.metastore.MetaStoreUtils.newInstance(MetaStoreUtils.java:1424) ... 12 more Caused by: MetaException(message:Could not connect to meta store using any of the URIs provided. Most recent failure: org.apache.thrift.transport.TTransportException: GSS initiate failed at org.apache.thrift.transport.TSaslTransport.sendAndThrowMessage(TSaslTransport.java:230) at org.apache.thrift.transport.TSaslTransport.open(TSaslTransport.java:306) at org.apache.thrift.transport.TSaslClientTransport.open(TSaslClientTransport.java:37) at org.apache.hadoop.hive.thrift.client.TUGIAssumingTransport$1.run(TUGIAssumingTransport.java:52) at org.apache.hadoop.hive.thrift.client.TUGIAssumingTransport$1.run(TUGIAssumingTransport.java:49) at java.security.AccessController.doPrivileged(Native Method) at javax.security.auth.Subject.doAs(Subject.java:415) at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1614) at org.apache.hadoop.hive.thrift.client.TUGIAssumingTransport.open(TUGIAssumingTransport.java:49) at org.apache.hadoop.hive.metastore.HiveMetaStoreClient.open(HiveMetaStoreClient.java:347) at org.apache.hadoop.hive.metastore.HiveMetaStoreClient.<init>(HiveMetaStoreClient.java:216) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:526) at org.apache.hadoop.hive.metastore.MetaStoreUtils.newInstance(MetaStoreUtils.java:1424) at org.apache.hadoop.hive.metastore.RetryingMetaStoreClient.<init>(RetryingMetaStoreClient.java:63) at org.apache.hadoop.hive.metastore.RetryingMetaStoreClient.getProxy(RetryingMetaStoreClient.java:73) at org.apache.hadoop.hive.ql.metadata.Hive.createMetaStoreClient(Hive.java:2462) at org.apache.hadoop.hive.ql.metadata.Hive.getMSC(Hive.java:2481) at org.apache.hadoop.hive.ql.session.SessionState.start(SessionState.java:341) at org.apache.hadoop.hive.cli.CliDriver.run(CliDriver.java:689) at org.apache.hadoop.hive.cli.CliDriver.main(CliDriver.java:633) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.apache.hadoop.util.RunJar.main(RunJar.java:212) ) at org.apache.hadoop.hive.metastore.HiveMetaStoreClient.open(HiveMetaStoreClient.java:393) at org.apache.hadoop.hive.metastore.HiveMetaStoreClient.<init>(HiveMetaStoreClient.java:216) ... 17 more {code} From container logs: {code} 2015-09-17 00:40:48,501 - ERROR [main:o.a.t.i.ServiceMain@103] - Exception thrown from service TwillContainerService [FAILED]. java.util.concurrent.ExecutionException: com.google.common.util.concurrent.UncheckedExecutionException: org.apache.hive.service.ServiceException: Unable to connect to MetaStore! at com.google.common.util.concurrent.AbstractFuture$Sync.getValue(AbstractFuture.java:294) ~[com.google.guava.guava-13.0.1.jar:na] at com.google.common.util.concurrent.AbstractFuture$Sync.get(AbstractFuture.java:281) ~[com.google.guava.guava-13.0.1.jar:na] at com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:116) ~[com.google.guava.guava-13.0.1.jar:na] at org.apache.twill.internal.ServiceMain.doMain(ServiceMain.java:99) ~[org.apache.twill.twill-yarn-0.6.0-incubating.jar:0.6.0-incubating] at org.apache.twill.internal.container.TwillContainerMain.main(TwillContainerMain.java:107) [org.apache.twill.twill-yarn-0.6.0-incubating.jar:0.6.0-incubating] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.7.0_75] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) ~[na:1.7.0_75] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.7.0_75] at java.lang.reflect.Method.invoke(Method.java:606) ~[na:1.7.0_75] at org.apache.twill.launcher.TwillLauncher.main(TwillLauncher.java:88) [launcher.2be487bf-8414-457a-a682-9326f69c2f51.jar:na] com.google.common.util.concurrent.UncheckedExecutionException: org.apache.hive.service.ServiceException: Unable to connect to MetaStore! at com.google.common.util.concurrent.Futures.wrapAndThrowUnchecked(Futures.java:1015) ~[com.google.guava.guava-13.0.1.jar:na] at com.google.common.util.concurrent.Futures.getUnchecked(Futures.java:1001) ~[com.google.guava.guava-13.0.1.jar:na] at com.google.common.util.concurrent.AbstractService.startAndWait(AbstractService.java:220) ~[com.google.guava.guava-13.0.1.jar:na] at com.google.common.util.concurrent.AbstractIdleService.startAndWait(AbstractIdleService.java:106) ~[com.google.guava.guava-13.0.1.jar:na] at co.cask.cdap.explore.executor.ExploreExecutorService.startUp(ExploreExecutorService.java:91) ~[co.cask.cdap.cdap-explore-3.2.0-SNAPSHOT.jar:na] at com.google.common.util.concurrent.AbstractIdleService$1$1.run(AbstractIdleService.java:43) ~[com.google.guava.guava-13.0.1.jar:na] at java.lang.Thread.run(Thread.java:745) ~[na:1.7.0_75] Caused by: org.apache.hive.service.ServiceException: Unable to connect to MetaStore! at org.apache.hive.service.cli.CLIService.start(CLIService.java:137) ~[hive-service-0.13.1-cdh5.2.6.jar-1442450390775.jar:0.13.1-cdh5.2.6] at co.cask.cdap.explore.service.hive.BaseHiveExploreService.startUp(BaseHiveExploreService.java:277) ~[co.cask.cdap.cdap-explore-3.2.0-SNAPSHOT.jar:na] ... 2 common frames omitted Caused by: org.apache.hadoop.hive.metastore.api.MetaException: Got exception: org.apache.hadoop.hive.metastore.api.MetaException javax.jdo.JDODataStoreException: Communications link failure The last packet successfully received from the server was 184,895 milliseconds ago. The last packet sent successfully to the server was 1 milliseconds ago. NestedThrowables: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure The last packet successfully received from the server was 184,895 milliseconds ago. The last packet sent successfully to the server was 1 milliseconds ago. at org.apache.hadoop.hive.metastore.MetaStoreUtils.logAndThrowMetaException(MetaStoreUtils.java:1116) ~[hive-metastore-0.13.1-cdh5.2.6.jar:0.13.1-cdh5.2.6] at org.apache.hadoop.hive.metastore.HiveMetaStoreClient.getDatabases(HiveMetaStoreClient.java:839) ~[hive-metastore-0.13.1-cdh5.2.6.jar:0.13.1-cdh5.2.6] at org.apache.hive.service.cli.CLIService.start(CLIService.java:135) ~[hive-service-0.13.1-cdh5.2.6.jar-1442450390775.jar:0.13.1-cdh5.2.6] ... 3 common frames omitted {code}
    via by Bhooshan Mogal,
    • java.util.concurrent.ExecutionException: org.jclouds.http.HttpResponseException: command: POST http://130.20.232.220:8774/v2/84ad49ccecf2478b9317b332c1490bd4/servers HTTP/1.1 failed with response: HTTP/1.1 400 null; content: [{"badRequest": {"message": "Multiple possible networks found, use a Network ID to be more specific.", "code": 400}}] at com.google.common.util.concurrent.AbstractFuture$Sync.getValue(AbstractFuture.java:306) at com.google.common.util.concurrent.AbstractFuture$Sync.get(AbstractFuture.java:293) at com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:116) at org.jclouds.concurrent.FutureIterables$1.run(FutureIterables.java:125) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744)

    Users with the same issue

    Unknown visitor1 times, last one,
    Agócs Tamás
    2 times, last one,
    Unknown visitor1 times, last one,
    kuldeep
    2 times, last one,
    Unknown visitor1 times, last one,
    2 more bugmates