CDD Cluster Tab Backing Store Properties Reference
Use this reference for the backing store properties.
For the related procedure, see Configuring Backing Store for Cache OM.
Property | Notes |
---|---|
Database Connection Properties | |
be.backingstore.recreateOnRecovery |
|
Set this property to true if the database pool size does not recover to the initial or minimum connection size, as defined by Min Size and Max Size properties (in
Configuring Backing Store for Cache OM ).
Default value is
|
|
Other properties | |
be.backingstore.useobjecttable |
|
The property when set to
true provides mappings for all entities in the cache. Object table is used to find the actual object either in the cache or in the backing store.
When this property is set to
Default value is
|
|
be.backingstore.optimize.reads |
|
Used with Microsoft SQL Server only.
Set the property to true to improve the runtime performance. Use
select * from dbo.D_MailerIndex with (nolock) where ... |
|
be.backingstore.optimize.writes |
|
Used with Microsoft SQL Server only.
Set the property to true to improve the runtime performance. Use
DELETE FROM dbo.D_Mailed WITH (ROWLOCK) where mailernumber = '12345678895' and time_created$ = 'somedate' |
|
be.backingstore.timestamp.useDataTimeZone |
|
Used when the backing store is enabled.
Set the property to true to ensure that the correct DateTime properties are retrieved when an agent’s time zone is changed and the agent is restarted. |
|
be.engine.cluster.recovery.threads |
|
Recovery threads are used when pre-loading the cache during startup.
For an explanation of pre-loading and other pre-loading controls, see Domain Objects Configuration. Default is
|
|
be.engine.cluster.recovery.distributed.strategy |
|
This property is used for Shared All and for Shared Nothing persistence.
Default value is:
Note: The seeder information (the current seeder list) is stored in the Shared Nothing persistence files during shutdown. This information is then used during startup or restart to perform recovery. If the cluster is exactly the same during startup (that is, exactly the same members are available and quorum is satisfied), then fast loading of the data is performed.
|
|
be.engine.cluster.recovery.distributed.batchsize |
|
When distributed batch recovery is enabled (be.engine.cluster.recovery.distributed.strategy=batch ), the recovery manager divides the target table into many smaller batches and assigns 1-to-n number of these batches to each node (for them to execute recovery).
This parameter provides an approximation to the size of each such batch. Since batches are defined using the target table's key field (for example, approximated using ID$ column), actual batch size will differ depending on the key distribution. Note: In case of legacy lookup strategy (default), the batch size is a numeric value as set by you to manage range but with new key-based lookup strategy ( be.engine.id.useLegacy=false ), the range rather is based on the timestamp.
Users can instead define
|
|
be.engine.cluster.useDBBatching |
|
Note
For use with cache aside and only when the parallel operations feature is used.
This property has no effect if
This property affects how all RTC transactions that a database writer thread takes from the database operations queue are written to the backing store:
For a guide to usage of this and other related properties, refer to the "Database Write Tuning Options for Cache Aside" section in the TIBCO BusinessEvents Architect’s Guide. Default value is
|
|
be.jdbc.multibyte.support |
|
You can specify whether multibyte characters are supported in the column values.
Set the value to
The default value is
|