java.util.concurrent.TimeoutException

Timed out after 600 seconds while waiting to discover the transaction service. Check the logs for the service to see what went wrong.*

Samebug tips0

We couldn't find tips for this exception.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web1

  • via Unknown by Teik Hooi Beh,
  • Stack trace

    • java.util.concurrent.TimeoutException: Timed out after 600 seconds while waiting to discover the transaction service. Check the logs for the service to see what went wrong.* 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.data2.dataset2.tx.TransactionalDatasetRegistry.startUp(TransactionalDatasetRegistry.java:56)[co.cask.cdap.cdap-data-fabric-3.4.3.jar:na] at co.cask.cdap.data2.datafabric.dataset.service.mds.MDSDatasetsRegistry.startUp(MDSDatasetsRegistry.java:49)[co.cask.cdap.cdap-data-fabric-3.4.3.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.8.0_102] Caused by: java.util.concurrent.TimeoutException: Timed out after 600 seconds while waiting to discover the transaction service. Check the logs for the service to see what went wrong.* at co.cask.cdap.data2.transaction.DistributedTransactionSystemClientService.startUp(DistributedTransactionSystemClientService.java:78)[co.cask.cdap.cdap-data-fabric-3.4.3.jar:na] ... 2 more

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    We couldn't find other users who have seen this exception.