MESOS: update known issues #17589
MESOS: update known issues #17589
Conversation
jdef
added
kind/documentation
|
Labelling this PR as size/L |
k8s-github-robot
added
the
size/L
| @@ -1,34 +1,120 @@ | |||
| ## Known Issues | |||
| ## DCOS Package Known Issues | |||
There was a problem hiding this comment.
It's super confusing have this as the page title when not all of the issues are DCOS specific.
It'd be ideal to just have a "Known Issues" page title, folowed bya table of contents that shows that there are general issues followed by dcos-specific issues. Thent he DCOS section can say that all of the general issues apply, and these additional issues also apply.
|
GCE e2e test build/test passed for commit b815269d75d21c46633f86ea6925bcaad93f25b2. |
|
GCE e2e test build/test passed for commit 041c84183df29d63acfe273b055ec1fab7c4f7a3. |
|
The ports stuff is kinda complicated. I'd really like to be able to easily answer from the user's perspective "What do I need to do about it?" for services, pods, and mesos slaves. The services section is really clear with the what and the how, without getting too deep into the why. I want something similar for pod config and mesos-slave config. The why should still be in the doc, but you don't want to get to the ports section and see the why first, see a giant list of long bullet points and not know what to do about it. |
|
|
||
| #### Runtime Configuration | ||
|
|
||
| - mesos: `--offer_timeout` : Duration of time before an offer is rescinded from a framework. |
There was a problem hiding this comment.
--offer-timeout? Didn't check, but I guess it's with a dash as well.
There was a problem hiding this comment.
--offer_timeout is correct (see http://mesos.apache.org/documentation/latest/configuration/)
|
GCE e2e test build/test passed for commit f36cb1383bd74bbd22471083d77de5a6cc4aac5d. |
| - availability of a resource offer that "fits" the pod (mesos master/slave); | ||
| - scheduler *backoff* (to avoid busy-looping) during pod scheduling (k8s-mesos scheduler) | ||
|
|
||
| We have tried to mitigate the second item by cancelling the backoff period if an offer arrives that fits a pod-in-waiting. |
|
@jdef left some nit comments, thanks for providing this! |
|
GCE e2e test build/test passed for commit de0c4f90e6e7a384003aaeb2d81368572359c990. |
|
lgtm. please squash |
- flag corrections - split into general vs. DCOS known issues - added lots of missing docs re: services, endpoints, upgrades, scheduler - clarified pod/ports section - cross-referenced open github issues where applicable
jdef
force-pushed
the
jdef_better_known_issues
branch
from
de0c4f9 to
e5b8095
Compare
jdef
added
the
lgtm
|
squished |
|
Continuous integration appears to have missed, closing and re-opening to trigger it |
|
GCE e2e test build/test passed for commit e5b8095. |
|
thanks @wojtek-t I didn't realize that label was there! |
|
@jdef - we are using "e2e-not-required" label for all PRs that cannot affect tests that are running as part of PR builder tests (in particular docs-only changes, etc.) |
|
Automatic merge from submit-queue |
Auto commit by PR queue bot
…_issues Auto commit by PR queue bot
…_issues Auto commit by PR queue bot
…_issues Auto commit by PR queue bot
…_issues Auto commit by PR queue bot
Better communicate known issues