[MXS-3380] MaxScale crash loop with cache filter + Redis Created: 2021-01-21 Updated: 2021-04-19 Resolved: 2021-02-12 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | cache |
| Affects Version/s: | 2.5.6 |
| Fix Version/s: | 2.5.8 |
| Type: | Bug | Priority: | Major |
| Reporter: | Todd Coker (Inactive) | Assignee: | Johan Wikman |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Environment: |
CentOS Linux release 7.7.1908 (Core) |
||
| Attachments: |
|
||||||||||||||||
| Issue Links: |
|
||||||||||||||||
| Sprint: | MXS-SPRINT-124 | ||||||||||||||||
| Description |
|
After enabling the cache filter with Redis on an RDBA customer's server (datacheck), MaxScale crashes. Log file attached (max-redis_error.txt). Customer runs Redis 5.0.6. Another MaxScale server (test) shows some similar errors but no crash. Same Redis version. The difference between datacheck and test is that datacheck has two app servers hitting it via a load balancer. They are not using cluster mode.
|
| Comments |
| Comment by Johan Wikman [ 2021-02-02 ] | ||
|
I have tried to repeat the problem using the following setups:
But everything works just fine. Coker Is the Redis server used by anybody else but MaxScale? | ||
| Comment by Johan Wikman [ 2021-02-02 ] | ||
|
I did find a bug that caused MaxScale to not immediately give up after
which will be fixed in 2.5.8. However, I suspect the cascading errors are caused by the unexpected NIL reply causing the reply handling to be aborted in the the middle. That then leads to the Redis requests performed by MaxScale and the responses it receives to get out of sync. | ||
| Comment by Johan Wikman [ 2021-02-05 ] | ||
|
I will close this now, even though I have not been able to repeat the behavior. However, storage_redis should now be much more resilient:
| ||
| Comment by Johan Wikman [ 2021-02-10 ] | ||
|
Coker What connector are they using? | ||
| Comment by Johan Wikman [ 2021-02-11 ] | ||
|
I could repeat the behaviour when using ConnectorJ and batching. | ||
| Comment by Johan Wikman [ 2021-02-12 ] | ||
|
Fixed by |