[AMQ-4211] Spooling to disk an a per destination usage limit basis rather than on shared usage

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Abandoned
• Affects Version/s: 5.7.0
• Component/s: Broker
• Labels: filependingmessagecursor limits memory pfc usage
• Assignee: Unassigned
• Reporter: Gary Tully
• Created: 07/Dec/12 12:55
• Updated: 13/Mar/22 14:08
• Resolved: 13/Mar/22 14:08

Description

Currently the filepending message cursor spools to disk when the system usage memory limit gets to 70% - the highWaterMark.
Why is this not based on the destination limit?

I think we need to investigate using the destination limit for the filepending message cursor so that it is trivially easy to get spooling to disk happen for a destination.
ie: set a policyEntry memory limit of 1mb on a destination and send it 1.2mb of messages and it will purge to disk and free up the 1mb.

To achieve this today, the 'system' memory limit needs to be 1mb and this effects all destinations and pfc (b/c of the shared parent).

note: if the destination does not have a limit, then the destination is limited by the parent system usage, so the global effect can be the same as before.