[MXS-1167] MaxScale tries to connect to internal services when loading database users Created: 2017-03-06 Updated: 2017-03-22 Resolved: 2017-03-22 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | schemarouter |
| Affects Version/s: | 2.1.0 |
| Fix Version/s: | 2.1.2 |
| Type: | Bug | Priority: | Minor |
| Reporter: | markus makela | Assignee: | markus makela |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||
| Sprint: | 2017-30 | ||||||||
| Description |
|
One use case for the schemarouter is to shard to internal MaxScale services. When this is done, MaxScale will log error messages about failed attempts to load the database users. The authenticator should skip the loading of the users at startup if the target server is a local MaxScale service. |
| Comments |
| Comment by markus makela [ 2017-03-20 ] |
|
The MaxScale core and authenticators handle the user permission checks and loading of the database users more intelligently. If a server points to an obviously local MaxScale service, both the permission checks and the loading of database users is skipped at startup. |