When Launching lots of tasks Journald is pegged.
In particular, it's this line:
INFO Task op 'LaunchTask' for instance [xxx] was REJECTED, reason 'xxx', rescheduling.
This needs to be cherry picked in Marathon 1.4
When Launching lots of tasks Journald is pegged.
In particular, it's this line:
INFO Task op 'LaunchTask' for instance [xxx] was REJECTED, reason 'xxx', rescheduling.
This needs to be cherry picked in Marathon 1.4
sbt test
Automatic diff as part of commit; lint not applicable. |
Automatic diff as part of commit; unit tests not applicable. |
I think the debug flag is not needed.
src/main/scala/mesosphere/marathon/core/launchqueue/impl/TaskLauncherActor.scala | ||
---|---|---|
237–239 | I thought isDebugEnabled is not necessary when using { }. Overall I'd like to have some overview when to use StrictLogging and when to use AkkaLogging. As @zen-dog showed we should not use AkkaLogging from within a future. This makes it sometimes hard when the future is used in an actor. |
Build has FAILED
Link to build: https://jenkins.mesosphere.com/service/jenkins/job/public-test-marathon-phabricator/535/
See console output for more information: https://jenkins.mesosphere.com/service/jenkins/job/public-test-marathon-phabricator/535/console
src/main/scala/mesosphere/marathon/core/launchqueue/impl/TaskLauncherActor.scala | ||
---|---|---|
237–239 | Removed. Probably a bigger topic of discussion. My take is: use the scala logger everywhere. |
Build is green https://jenkins.mesosphere.com/service/jenkins/job/public-test-marathon-phabricator/538/ for more details.
src/main/scala/mesosphere/marathon/core/launchqueue/impl/TaskLauncherActor.scala | ||
---|---|---|
237–239 | +1 |
I thought isDebugEnabled is not necessary when using { }.
Overall I'd like to have some overview when to use StrictLogging and when to use AkkaLogging. As @zen-dog showed we should not use AkkaLogging from within a future. This makes it sometimes hard when the future is used in an actor.