Trigger criteria for file_destination_defrag .
Article ID: KB0094648
Updated On:
| Products | Versions |
|---|---|
| TIBCO Enterprise Message Service | - |
| Not Applicable | - |
Description
Resolution:
Description:
= = = = = = =
The trigger that enables the feature is that the queue's consumer has fallen behind. Tracking messages for defrag starts when the queue backlog reaches the value of destination_backlog_swapout, which by default is 1024 .
Once a batch of messages have been assembled that total the size set by the file_destination_defrag option, some or all of the messages are compacted and swap out.
When the consumer comes back online and catches up to the point where the backlog is below destination_backlog_swapout, auto compaction stops.
Environment:
= = = = = = =
All
Description:
= = = = = = =
The trigger that enables the feature is that the queue's consumer has fallen behind. Tracking messages for defrag starts when the queue backlog reaches the value of destination_backlog_swapout, which by default is 1024 .
Once a batch of messages have been assembled that total the size set by the file_destination_defrag option, some or all of the messages are compacted and swap out.
When the consumer comes back online and catches up to the point where the backlog is below destination_backlog_swapout, auto compaction stops.
Environment:
= = = = = = =
All
Issue/Introduction
Trigger criteria for file_destination_defrag .
Feedback
Yes
No
Powered by
