| Summary: | Embedded mysql/postgresql is stopped after stopping and restarting app | ||
|---|---|---|---|
| Product: | OKD | Reporter: | jizhao |
| Component: | Containers | Assignee: | Dan McPherson <dmcphers> |
| Status: | CLOSED NOTABUG | QA Contact: | libra bugs <libra-bugs> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 2.x | CC: | szhou |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-01-31 17:07:39 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
jizhao
2012-01-31 05:24:03 UTC
This is as designed. Stop stops everything. The thinking being no one wants to have to stop multiple services to stop everything. Start starts everything. Again the thinking being they probably want their app to be running. And if that's not the case they can stop individual pieces after. But restart would most often be used to retry something. And you usually know what you want to retry. Either you made a code change or a db change or whatever. And you are hoping a restart will fix it. So we leave the control on restart on an individual component level. |