[MXS-436] Invalid threads argument is ignored and MaxScale starts with one thread Created: 2015-10-31 Updated: 2015-11-02 Resolved: 2015-11-02 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | Core |
| Affects Version/s: | 1.2.1 |
| Fix Version/s: | 1.3.0 |
| Type: | Bug | Priority: | Minor |
| Reporter: | markus makela | Assignee: | Johan Wikman |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Description |
|
If MaxScale is started with a threads parameter of less than one, MaxScale will start but will log the following message to the message log:
This should be detected and logged that an invalid value is used. - And MaxScale process should not be started if less than one is passed for threads parameter |
| Comments |
| Comment by Dipti Joshi (Inactive) [ 2015-11-02 ] |
|
markus makela, johan.wikman Should MaxScale be not started in case of thread count parameter of -1 or does it start with a default number of threads ? Thanks |
| Comment by markus makela [ 2015-11-02 ] |
|
It shouldn't start at all. |
| Comment by Johan Wikman [ 2015-11-02 ] |
|
A general policy regarding configuration issues is needed.
As far as the threads issue is concerned a reasonable approach would be:
|