unable to run wordCountExample

[jrabary]

I get the following error when trying to run the wordCount example :

curl -d "input.string = a b c a b see" 'localhost:8090/jobs?appName=test&classPath=spark.jobserver.WordCountExample'
{
  "status": "ERROR",
  "result": {
    "message": "Timed out",
    "errorClass": "akka.pattern.AskTimeoutException",
    "stack": ["akka.pattern.PromiseActorRef$$anonfun$1.apply$mcV$sp(AskSupport.scala:334)", "akka.actor.Scheduler$$anon$11.run(Scheduler.scala:118)", "scala.concurrent.Future$InternalCallbackExecutor$.scala$concurrent$Future$InternalCallbackExecutor$$unbatchedExecute(Future.scala:694)", "scala.concurrent.Future$InternalCallbackExecutor$.execute(Future.scala:691)", "akka.actor.LightArrayRevolverScheduler$TaskHolder.executeTask(Scheduler.scala:455)", "akka.actor.LightArrayRevolverScheduler$$anon$12.executeBucket$1(Scheduler.scala:407)", "akka.actor.LightArrayRevolverScheduler$$anon$12.nextTick(Scheduler.scala:411)", "akka.actor.LightArrayRevolverScheduler$$anon$12.run(Scheduler.scala:363)", "java.lang.Thread.run(Thread.java:745)"]
  }

And here is the log

[2014-10-09 21:38:36,049] INFO  .jobserver.RddManagerActor [] [akka://JobServer/user/context-    supervisor/9ca13123-spark.jobserver.WordCountExample/rdd-manager-actor] - Starting actor spark.  jobserver.RddManagerActor
 [2014-10-09 21:38:36,049] INFO  ocalContextSupervisorActor [] [] - SparkContext 9ca13123-spark.  jobserver.WordCountExample initialized
 [2014-10-09 21:38:36,052] INFO  a.actor.DeadLetterActorRef [] [akka://JobServer/deadLetters] -   Message [scala.Tuple2] from Actor[akka://JobServer/user/context-supervisor#-621627427] to        Actor[akka://JobServer/deadLetters] was not delivered. [1] dead letters encountered. This        logging can be turned off or adjusted with configuration settings 'akka.log-dead-letters' and    'akka.log-dead-letters-during-shutdown'.

[david-resnick]

I'm not sure where it is being applied but the WebApi implicit val ShortTimeout of 3 seconds is what is timing out, while waiting for local context creation (which takes about 5 seconds). Increasing it to 10 seconds allows enough time for the context to be created and the job to be launched.

There is no indication of the timeout in the log while the local context is being created. Instead, the context is left waiting; subsequently launching the same job in that context succeeds with the context being closed after job completion.

The timeout value should be configurable and the timeout should be logged.

[velvia]

Agreed with both.

On Thu, Nov 20, 2014 at 5:33 AM, David Resnick [email protected]
wrote:

I'm not sure where it is being applied but the WebApi implicit val
ShortTimeout of 3 seconds is what is timing out, while waiting for local
context creation (which takes about 5 seconds). Increasing it to 10 seconds
allows enough time for the context to be created and the job to be launched.

There is no indication of the timeout in the log while the local context
is being created. Instead, the context is left waiting; subsequently
launching the same job in that context succeeds with the context being
closed after job completion.

The timeout value should be configurable and the timeout should be logged.

—
Reply to this email directly or view it on GitHub
#70 (comment)
.

The fruit of silence is prayer;
the fruit of prayer is faith;
the fruit of faith is love;
the fruit of love is service;
the fruit of service is peace. -- Mother Teresa

[anshulsin]

I'm facing the same issue. Also asked on google group :
https://groups.google.com/forum/#!topic/spark-jobserver/BP3mnPe9V0A

Any updates?