[MXS-3617] writeq throttling can lose response packets Created: 2021-06-16 Updated: 2021-11-10 Resolved: 2021-06-18 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | Core |
| Affects Version/s: | 2.5.13 |
| Fix Version/s: | 2.4.19, 2.5.14 |
| Type: | Bug | Priority: | Major |
| Reporter: | markus makela | Assignee: | markus makela |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Description |
|
If the client sends very large amounts of data and the backend writeq_high_water is hit, the client is removed from epoll until the backend buffers fall under writeq_low_water. During this time if a backend sends a response, it is discarded by the backend protocol code. This can manifest itself as a hang during large batch uploads using the MariaDB JDBC or Nodejs connectors. |