{"action":"closed","issue":{"url":"https://api.github.com/repos/yahoo/kafka-manager/issues/143","labels_url":"https://api.github.com/repos/yahoo/kafka-manager/issues/143/labels{/name}","comments_url":"https://api.github.com/repos/yahoo/kafka-manager/issues/143/comments","events_url":"https://api.github.com/repos/yahoo/kafka-manager/issues/143/events","html_url":"https://github.com/yahoo/kafka-manager/issues/143","id":112644021,"number":143,"title":"Kafka Manager API timing out","user":{"login":"josephfrancis","id":857070,"avatar_url":"https://avatars.githubusercontent.com/u/857070?v=3","gravatar_id":"","url":"https://api.github.com/users/josephfrancis","html_url":"https://github.com/josephfrancis","followers_url":"https://api.github.com/users/josephfrancis/followers","following_url":"https://api.github.com/users/josephfrancis/following{/other_user}","gists_url":"https://api.github.com/users/josephfrancis/gists{/gist_id}","starred_url":"https://api.github.com/users/josephfrancis/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/josephfrancis/subscriptions","organizations_url":"https://api.github.com/users/josephfrancis/orgs","repos_url":"https://api.github.com/users/josephfrancis/repos","events_url":"https://api.github.com/users/josephfrancis/events{/privacy}","received_events_url":"https://api.github.com/users/josephfrancis/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-10-21T17:51:58Z","updated_at":"2015-10-26T11:23:11Z","closed_at":"2015-10-26T11:23:11Z","body":"I have deployed kafka manager in several environments, while it works in all non production environments it keeps timing out when we try to access any topic level information in the production environment.\r\n```\r\n2015-10-21 17:16:46,276 - [ERROR] - from kafka.manager.ApiError in pool-3-thread-2 \r\nerror : Ask timed out on [ActorSelection[Anchor(akka://kafka-manager-system/), Path(/user/kafka-manager)]] after [90000 ms]\r\nakka.pattern.AskTimeoutException: Ask timed out on [ActorSelection[Anchor(akka://kafka-manager-system/), Path(/user/kafka-manager)]] after [90000 ms]\r\n        at akka.pattern.PromiseActorRef$$anonfun$1.apply$mcV$sp(AskSupport.scala:334) ~[com.typesafe.akka.akka-actor_2.11-2.3.10.jar:na]\r\n        at akka.actor.Scheduler$$anon$7.run(Scheduler.scala:117) ~[com.typesafe.akka.akka-actor_2.11-2.3.10.jar:na]\r\n        at scala.concurrent.Future$InternalCallbackExecutor$.unbatchedExecute(Future.scala:599) ~[org.scala-lang.scala-library-2.11.7.jar:na]\r\n        at scala.concurrent.BatchingExecutor$class.execute(BatchingExecutor.scala:109) ~[org.scala-lang.scala-library-2.11.7.jar:na]\r\n        at scala.concurrent.Future$InternalCallbackExecutor$.execute(Future.scala:597) ~[org.scala-lang.scala-library-2.11.7.jar:na]\r\n        at akka.actor.LightArrayRevolverScheduler$TaskHolder.executeTask(Scheduler.scala:467) ~[com.typesafe.akka.akka-actor_2.11-2.3.10.jar:na]\r\n        at akka.actor.LightArrayRevolverScheduler$$anon$8.executeBucket$1(Scheduler.scala:419) ~[com.typesafe.akka.akka-actor_2.11-2.3.10.jar:na]\r\n        at akka.actor.LightArrayRevolverScheduler$$anon$8.nextTick(Scheduler.scala:423) ~[com.typesafe.akka.akka-actor_2.11-2.3.10.jar:na]\r\n        at akka.actor.LightArrayRevolverScheduler$$anon$8.run(Scheduler.scala:375) ~[com.typesafe.akka.akka-actor_2.11-2.3.10.jar:na]\r\n        at java.lang.Thread.run(Thread.java:745) [na:1.7.0_85]\r\n\r\n```\r\n\r\n* I can manually connect to kafka and zookeeper fine from the box where kafka manager is installed. I have also seen kafka manager to work a couple of times without timeouts.\r\n* I'm trying to connect to a 10 node kafka cluster + 5 node zookeeper cluster.\r\n* Kafka manager also gets into a stuck state if I try to update the cluster information. \r\n* Also tried with a timeout of 2 mins as against the default 5 secs, but no joy.\r\n \r\nI can't seem to understand why there would be timeouts especially since the kafka manager and kafka nodes are all in the same internal network. Any pointers in finding the root cause? "}}