Details here: https://github.com/mesosphere/marathon/pull/5487
Details
- Reviewers
zen-dog jenkins timcharper ichernetsky jdef jeschkies - Commits
- rMARATHONbdbf2133aece: community debug of proxy failure to leader. @xperimental code moved to master…
rMARATHON6f5e6fc14378: community debug of proxy failure to leader. @xperimental code moved to master… - JIRA Issues
- JIRA MARATHON-7724 Handle timeout error when proxying to leader
run tests
Diff Detail
- Repository
- rMARATHON marathon
- Lint
Automatic diff as part of commit; lint not applicable. - Unit
Automatic diff as part of commit; unit tests not applicable.
You can create a DC/OS with your patched Marathon by creating a new pull
request with the following changes in buildinfo.json:
\\ ٩( ᐛ )و //
src/main/scala/mesosphere/marathon/api/LeaderProxyFilter.scala | ||
---|---|---|
297–298 | Just wondering, shouldn't we log the errors? |
src/main/scala/mesosphere/marathon/api/LeaderProxyFilter.scala | ||
---|---|---|
297–298 | you are right! thx! |
Error message:
Stage Compile and Test failed.
(๑′°︿°๑)
Error message:
Stage Compile and Test failed.
(๑′°︿°๑)
Error message:
Stage Compile and Test failed.
(๑′°︿°๑)
left additional comments here https://github.com/mesosphere/marathon/pull/5487#issuecomment-324683454
src/main/scala/mesosphere/marathon/api/LeaderProxyFilter.scala | ||
---|---|---|
303 | a response may have already been committed in this case. i'm pretty sure that these additional exception catches should be limited to the copyRequestToConnection(...) call. copyConnectionResponse already handles failures. |
Error message:
Stage Compile and Test failed.
(๑′°︿°๑)
Error message:
Stage Compile and Test failed.
(๑′°︿°๑)
Error message:
Stage Compile and Test failed.
(๑′°︿°๑)
You can create a DC/OS with your patched Marathon by creating a new pull
request with the following changes in buildinfo.json:
Just wondering, shouldn't we log the errors?