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

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

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

Solutions on the web1321

  • via Google Groups by Teik Hooi Beh, 6 months ago
    Timed out after 600 seconds while waiting to discover the transaction service. Check the logs for the service to see what went wrong.*
  • Timed out waiting for the service connection
  • via GitHub by kiril-akshonau
    , 7 months ago
    Timeout after waiting 5 seconds to acquire the lock.
  • 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 co.cask.cdap.data.runtime.main.MasterServiceMain$2.leader(MasterServiceMain.java:432)[co.cask.cdap.cdap-master-3.4.3.jar:na] at org.apache.twill.internal.zookeeper.LeaderElection.becomeLeader(LeaderElection.java:229)[org.apache.twill.twill-zookeeper-0.7.0-incubating.jar:0.7.0-incubating] at org.apache.twill.internal.zookeeper.LeaderElection.access$1800(LeaderElection.java:53)[org.apache.twill.twill-zookeeper-0.7.0-incubating.jar:0.7.0-incubating] at org.apache.twill.internal.zookeeper.LeaderElection$5.onSuccess(LeaderElection.java:207)[org.apache.twill.twill-zookeeper-0.7.0-incubating.jar:0.7.0-incubating] at org.apache.twill.internal.zookeeper.LeaderElection$5.onSuccess(LeaderElection.java:186)[org.apache.twill.twill-zookeeper-0.7.0-incubating.jar:0.7.0-incubating] at com.google.common.util.concurrent.Futures$6.run(Futures.java:799)[com.google.guava.guava-13.0.1.jar:na] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[na:1.8.0_102] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[na:1.8.0_102] at java.lang.Thread.run(Thread.java:745)[na:1.8.0_102]

    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

    You’re the first here who have seen this exception.