search

mesosphere / marathon

Deploy and manage containers (including Docker) on top of Apache Mesos at scale.
https://mesosphere.github.io/marathon/
Apache License 2.0
4.07k stars 845 forks source link

Different output when using headers application/json #1357

Closed deric closed 9 years ago

deric commented 9 years ago

Marathon API list tasks that are being deployed with header application/json:

curl -H 'Accept: application/json' http://localhost:8080/v2/tasks | grep -i task-being-deployed | wc -l
12

while same GET request without JSON header would not include those tasks

curl http://localhost:8080/v2/tasks | grep -i task-being-deployed | wc -l
0

In log the tasks appears as:

[2015-04-01 14:08:38,554] WARN App task-being-deployed.7fc25f41-fc76-40ee-a101-a0d241ac1f8f exists in TaskTracker, but not App store. The app was likely terminated. Will now expunge. (mesosphere.marathon.SchedulerActions:461)
[2015-04-01 14:08:38,554] INFO Killing task task-being-deployed.7fc25f41-fc76-40ee-a101-a0d241ac1f8f.8e566f4a-d36e-11e4-b4d6-cecf105f3510 (mesosphere.marathon.SchedulerActions:466)

Marathon 0.8.1

aquamatthias commented 9 years ago

The default output for this endpoint (without defining content type) was text/plain. We changed it to json output. So it should work the same way.