[MXS-3400] maxscale crash with memcache on ubuntu 20 Created: 2021-02-08 Updated: 2021-02-12 Resolved: 2021-02-12 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | cache |
| Affects Version/s: | 2.5.7 |
| Fix Version/s: | 2.5.8 |
| Type: | Bug | Priority: | Major |
| Reporter: | Isaac Venn (Inactive) | Assignee: | Johan Wikman |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Environment: |
Ubuntu 20 on AWS |
||
| Attachments: |
maxscale-arreva.tar.gz
|
||||||||||||||||
| Issue Links: |
|
||||||||||||||||
| Description |
|
Client is having trouble with maxscale crashing regardless of the caching mechanism being used. They tried redis and had regular crashes so they moved to memcache and are having the same issue. |
| Comments |
| Comment by Johan Wikman [ 2021-02-10 ] |
|
ivenn Could they try with in memory caching as well? If there are no issues, then it would be pretty certain the problem specific to distributed storage What connector do they use? |
| Comment by Isaac Venn (Inactive) [ 2021-02-10 ] |
|
They use J connector 2.4.2. I have configured the in-memory cache and restarted their host. We'll see if we get a crash in the next few days. |
| Comment by Isaac Venn (Inactive) [ 2021-02-11 ] |
|
johan.wikman after switching it from memcache to in-memory, they have not had a crash since. |
| Comment by Johan Wikman [ 2021-02-11 ] |
|
ivennThat's actually somewhat surprising... What about the log, any complaints about the cache receiving data from the backend when none was expected? |
| Comment by Johan Wikman [ 2021-02-12 ] |
|
Fixed by |