[MXS-352] With no backend connection, services aren't started Created: 2015-09-07 Updated: 2015-10-07 Resolved: 2015-10-07 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | Core |
| Affects Version/s: | 1.2.0 |
| Fix Version/s: | 1.3.0 |
| Type: | Bug | Priority: | Minor |
| Reporter: | markus makela | Assignee: | markus makela |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Description |
|
When MaxScale is started and there is no connectivity to the backend servers, services which fail to start are never restarted even if connectivity is achieved. The maxadmin command restart service will put the service into started state but connections to it will not be possible. A use-case is that the cluster and maxscale crash, after which maxscale starts before the cluster, when all servers are still down. |
| Comments |
| Comment by Dipti Joshi (Inactive) [ 2015-09-07 ] |
|
What would be the work around in this case before this is fixed ? - |
| Comment by markus makela [ 2015-09-08 ] |
|
Restarting MaxScale once there is connectivity to the servers will fix it. |
| Comment by Johan Wikman [ 2015-09-08 ] |
|
What does "there is no connectivity to the backend servers" actually mean? That's an extraordinary situation? |