Details
-
Regression
-
Status: Resolved
-
Critical
-
Resolution: Fixed
-
None
-
None
Description
In a Thor configuration with multiple channels handling rows with child datasets, the row managers per slave and the allocator caching mechanism conspire to cause the row destructor callback to fail to find it's cached allocator.
This was because each slave channel had it's own cache, but the roxiemem slave row managers were sharing the global one.
Attachments
Issue Links
- relates to
-
HPCC-15582 Thor performance issue with row allocator / channel cache
-
- Resolved
-