Closed shijinkui closed 8 years ago
can't rollback the deployment, and create new application, it remain wainting state
Hi @shijinkui
can you please specify the versions of Marathon and Mesos you're trying to run this on? Also, the JSON for the application definition would help.
{
"id": "/etl/db.abc",
"cmd": "$SPARK_HOME/bin/spark-submit --name db.xxx --class ETL --master mesos://xxx:5050 --deploy-mode client --executor-memory 8g --total-executor-cores 1 streaming-etl-assembly-2.11.7-1.0.jar",
"cpus": 1,
"mem": 3072,
"disk": 3072,
"instances": 1,
"env": {
"JAVA_HOME": "/data/program/java",
"SPARK_HOME": "/data/program/spark",
"HADOOP_HOME": "/data/program/hdfs",
"HADOOP_CONF_DIR": "/data/program/hdfs/etc/hadoop"
},
"portDefinitions": [
{
"port": 10002,
"protocol": "tcp",
"labels": {}
}
],
"uris": [
"http://jar.xxx.xxx.info/streaming-etl-assembly-2.11.7-1.0.jar"
],
"fetch": [
{
"uri": "http://jar.xxx.xxx.info/streaming-etl-assembly-2.11.7-1.0.jar",
"extract": true,
"executable": false,
"cache": false
}
]
}
when i upgrate to v1.1.1, the problem also exist
[2016-04-19 11:33:29,419] ERROR Deployment of / failed (mesosphere.marathon.MarathonSchedulerActor:marathon-akka.actor.default-dispatcher-11)
mesosphere.marathon.DeploymentCanceledException: The upgrade has been cancelled
at mesosphere.marathon.upgrade.DeploymentManager$$anonfun$receive$1$$anonfun$3.apply(DeploymentManager.scala:53) ~[marathon-assembly-1.1.1.jar:1.1.1]
at mesosphere.marathon.upgrade.DeploymentManager$$anonfun$receive$1$$anonfun$3.apply(DeploymentManager.scala:52) ~[marathon-assembly-1.1.1.jar:1.1.1]
at scala.collection.TraversableLike$$anonfun$map$1.apply(TraversableLike.scala:245) ~[marathon-assembly-1.1.1.jar:1.1.1]
at scala.collection.TraversableLike$$anonfun$map$1.apply(TraversableLike.scala:245) ~[marathon-assembly-1.1.1.jar:1.1.1]
at scala.collection.immutable.List.foreach(List.scala:381) ~[marathon-assembly-1.1.1.jar:1.1.1]
at scala.collection.TraversableLike$class.map(TraversableLike.scala:245) ~[marathon-assembly-1.1.1.jar:1.1.1]
at scala.collection.immutable.List.map(List.scala:285) ~[marathon-assembly-1.1.1.jar:1.1.1]
at mesosphere.marathon.upgrade.DeploymentManager$$anonfun$receive$1.applyOrElse(DeploymentManager.scala:52) ~[marathon-assembly-1.1.1.jar:1.1.1]
at akka.actor.Actor$class.aroundReceive(Actor.scala:465) ~[marathon-assembly-1.1.1.jar:1.1.1]
at mesosphere.marathon.upgrade.DeploymentManager.aroundReceive(DeploymentManager.scala:23) ~[marathon-assembly-1.1.1.jar:1.1.1]
at akka.actor.ActorCell.receiveMessage(ActorCell.scala:516) [marathon-assembly-1.1.1.jar:1.1.1]
at akka.actor.ActorCell.invoke(ActorCell.scala:487) [marathon-assembly-1.1.1.jar:1.1.1]
at akka.dispatch.Mailbox.processMailbox(Mailbox.scala:254) [marathon-assembly-1.1.1.jar:1.1.1]
at akka.dispatch.Mailbox.run(Mailbox.scala:221) [marathon-assembly-1.1.1.jar:1.1.1]
at akka.dispatch.Mailbox.exec(Mailbox.scala:231) [marathon-assembly-1.1.1.jar:1.1.1]
at scala.concurrent.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260) [marathon-assembly-1.1.1.jar:1.1.1]
at scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1339) [marathon-assembly-1.1.1.jar:1.1.1]
at scala.concurrent.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979) [marathon-assembly-1.1.1.jar:1.1.1]
at scala.concurrent.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107) [marathon-assembly-1.1.1.jar:1.1.1]
Just a side note: you can remove the "uris"
node – uris
have been deprecated in favor of using the Mesos fetcher cache as you do with "fetch"
. I don't think that's the problem though.
@meichstedt thanks.
i prefer to use http
service for jar download.
@pierlo-upitup @meichstedt it alway wait. how can marathon be debug local
when i restart the mesos master, marathon's deployment can go on. it's very strange. close this issue.