marathon

marathon copied to clipboard

hello, When publishing with marathon,Occasionally, the service is stuck, phenomenon： 1. The service is not moving for a long time 2. need to kill a node to recover ths.

zhangtao3678

Hello, It seems that there's no way to configure the SSL Context, e.g. the list of accepted ciphers... Am I wrong?

maricaantonacci

timcharper

this constraint was working 1.9.136 "constraints": [["@zone", "IS", "rack1"], ["hostname", "GROUP_BY"]]

f1-outsourcing

there is no release 1.11 nor 1.11.24

3

There is already quite some time a 1.11 on docker, what release/tag corresponds with the docker images 1.11.24? Am I correct to understand that the docker images are build from...

f1-outsourcing

sbt.librarymanagement.ResolveException: Error downloading org.apache.mesos:mesos:1.11.0-SNAPSHOT

2

I can build 1.10 like this, but the 1.11 comes with this error download pom file. ``` git checkout releases/1.11 sbt compile ``` download error: Caught java.io.IOException: Server returned HTTP...

f1-outsourcing

"val lines = comments.flatMap(_.lines)" in FieldT.scala: type mismatch

1

Hello, Most of the version fails to build with the following error: ``` [error] /home/acecile/packaging/marathon/marathon-1.9.109/build/type-generator/src/main/scala/mesosphere/raml/ir/FieldT.scala:76:36: type mismatch; [error] found : java.util.stream.Stream[String] [error] required: scala.collection.GenTraversableOnce[?] [error] val lines = comments.flatMap(_.lines) ```...

eLvErDe

some help with marathon 1.11 and mvp csi secrets, do not seem to be send.

1

I have been looking forward to the update of mesos offering this mvp csi, mainly to finally be able to use ceph. But unfortunately I am still not able to...

f1-outsourcing

docker image is having outdated java

5

When trying to solve this issue[1] I noticed that your docker image is having an outdated java 1.8.222, current one is 1.8.0.252 which is from Apr 29. That is from...

f1-outsourcing

Scale checks are done regularly, to validate that running instances number matches expected number of instances in runSpec. There are two cases: * There are missing instances, in that case...

Lqp1