[MXS-1386] Clean up DCB Created: 2017-09-04 Updated: 2019-10-10 Resolved: 2019-09-26 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | Core |
| Affects Version/s: | None |
| Fix Version/s: | 2.5.0 |
| Type: | Task | Priority: | Major |
| Reporter: | Johan Wikman | Assignee: | Johan Wikman |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Epic Link: | API Improvements |
| Sprint: | MXS-SPRINT-87, MXS-SPRINT-88, MXS-SPRINT-89, MXS-SPRINT-90, MXS-SPRINT-91 |
| Description |
|
Currently there is some ambiguity about the DCB and session ownership and how a session shutdown is triggered. For instance, when calling dcb_close the dcb will also be deleted, except if it is a client dcb in which case it will be closed but not deleted and then explicitly freed in session_free. The ownership relations should be cleaned up so that there is no ambiguity. |
| Comments |
| Comment by markus makela [ 2019-05-28 ] |
|
Partially done in 2.4 with the refactoring of session creation. |