Is there a configuration option available which sets size limit for EMS datastores files?
Article ID: KB0090409
Updated On:
| Products | Versions |
|---|---|
| TIBCO Enterprise Message Service | - |
| Not Applicable | - |
Description
Resolution:
Question:
= = = = = = =
Is there a configuration option available which sets an upper limit for EMS datastores for EMS instance? Can we limit these datastore files to grow up to certain size?
Answer:
= = = = = = =
There is no limitation on the datastore file size for 32 and/or 64-bit EMS servers. These files can grow to an extent of the free space available in a hard drive. The maximum datastore file size is determined by the operating system (OS) and the file system.
The EMS server relies on the max_msg_memory and/or reserve_memory properties to be set appropriately in order to prevent datastore files from growing too large. Also, even if there are very few pending messages in a datastore files, the file size may be proportionately larger. This situation arises when the data in the datastore files is fragmented. A large fragmented datastore file may adversely impact EMS performance. We recommend enabling store_truncate parameter in EMS server’s main config file (default tibemsd.conf) and schedule periodic compact on datastores during regular maintenance downtime, off-business hours or when there is very less load on the server. The compact command blocks all EMS operations.
Question:
= = = = = = =
Is there a configuration option available which sets an upper limit for EMS datastores for EMS instance? Can we limit these datastore files to grow up to certain size?
Answer:
= = = = = = =
There is no limitation on the datastore file size for 32 and/or 64-bit EMS servers. These files can grow to an extent of the free space available in a hard drive. The maximum datastore file size is determined by the operating system (OS) and the file system.
The EMS server relies on the max_msg_memory and/or reserve_memory properties to be set appropriately in order to prevent datastore files from growing too large. Also, even if there are very few pending messages in a datastore files, the file size may be proportionately larger. This situation arises when the data in the datastore files is fragmented. A large fragmented datastore file may adversely impact EMS performance. We recommend enabling store_truncate parameter in EMS server’s main config file (default tibemsd.conf) and schedule periodic compact on datastores during regular maintenance downtime, off-business hours or when there is very less load on the server. The compact command blocks all EMS operations.
Issue/Introduction
Is there a configuration option available which sets size limit for EMS datastores files?
Feedback
Yes
No
Powered by
