[MXS-431] Backend authentication fails with schemarouter Created: 2015-10-28 Updated: 2015-11-03 Resolved: 2015-11-03 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | schemarouter |
| Affects Version/s: | 1.2.1 |
| Fix Version/s: | 1.3.0 |
| Type: | Bug | Priority: | Major |
| Reporter: | markus makela | Assignee: | markus makela |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Description |
|
The schemarouter sometimes fails to properly clear the client session's default database resulting in errors from the backend if the database doesn't exist. A good example is when a user connects to the schemarouter with a default database of db1. This database does not exist on all of the backend servers so to allow connections to all shards, the schemarouter clears the client protocols default database flags. Later the schemarouter sends a USE db1 query to the correct shard. |
| Comments |
| Comment by markus makela [ 2015-10-29 ] |
|
The cause for this was the use of a shared protocol structure and updating the default database when one of more backend connections were still being processed. This resulted in an unknown database being used in the authentication packet. |