CDD Cluster Tab DataGrid Properties Reference
DataGrid properties can be configured using the CDD Cluster Tab. Refer to the following table for a list of properties that you can use to retrieve data from the DataGrid.
Property | Notes |
---|---|
be.engine.cluster.as.aggregate.prefetch.size | |
When queries are executed against TIBCO DataGrid via the aggregate query functions (found under Query.Datagrid.Aggregate), you can define the number of entries to prefetch for optimum performance.
Although TIBCO BusinessEvents has a default value that provides best performance for general use cases, you can adjust the value to meet your specific use case needs. Valid values are any positive long numbers or -1 (-1 = prefetch all). Default value is -1. |
|
be.engine.cluster.as.browser.prefetch.size | |
When queries are executed against TIBCO DataGrid via any 'select' type of queries, you can define the number of entries to prefetch for optimum performance.
Although TIBCO BusinessEvents has a default value that provides best performance for general use cases, you can adjust the value to meet your specific use case needs. Valid values are any positive long number or -1 (-1 = prefetch all). Default value is -1. |
|
be.engine.cluster.as.lookup.prefetch.size | |
When queries are executed against TIBCO DataGrid via getByExtByUri() or by loadByExtIdByUri() functions (which either return 1 or no results), you an define the number of entries to prefetch for optimum performance.
Although TIBCO BusinessEvents has a default value that provides best performance for general use cases, you can adjust the value to meet your speficic use case needs. Default value is 0(zero) which prefetches nothing. |
|
be.engine.cluster.as.member.timeout | |
The timeout parameter specifies how many milliseonds TIBCO DataGrid will wait for a member to reconnect, if it loses connection to the metaspace. The default value is 30000 milliseconds. | |
be.engine.channel.as.querylimit | |
You can control the query limit for an ActiveSpaces channel using the
querylimit property. You can set this property in CDD so that the channel can receive entries beyond 10000 (default in TIBCO ActiveSpaces).
The default value in TIBCO BusinessEvents is -1, which indicates no limit on queries. |
|
be.engine.cluster.as.suspend.threshold | |
The threshold parameter specifies the number of host connections that can be lost before the cluster moves into a suspended state. When the cluster is suspended, members cannot leave or join the cluster. If connectivity is lost for a seeder member of a space, doing a read or write for the space might cause a protocol timeout. The default value is -1, which indicates that the cluster is never suspended. | |
be.engine.cluster.as.file.sync.interval | |
The amount of time (in milliseconds) to wait between persists to the data store when asynchronous shared-nothing persistence is used. The set value can be viewed as the
File Sync Interval property value in
as-admin.
The default value is 10000 milliseconds. |
|
be.engine.cluster.as.discover.url | |
The discover URL specifies how an engine (node) listens for discovery requests from nodes attempting to join the cluster. PGM protocol is supported for multicast discovery. TCP protocol is supported for unicast (well-known address) discovery. Configuration is different for multicast and unicast discovery. See
DataGrid Discover URL for details.
The default value for multicast equates to: tibpgm://7888/;239.8.8.9/ |
|
be.engine.cluster.as.hostaware.enable | |
By default, this property is true (or enabled).
|
|
be.engine.cluster.as.hostaware.hostname | |
Hostnames that are used in identifying members (and therefore naming SharedNothing file/folders), are generated from underlying OS. If you would like to assign hostnames manually instead, for reasons such as hostname/machine changes, testing so on, then provide hostnames in the CDD at each PU level using be.engine.cluster.as.hostaware.hostname property. | |
be.engine.cluster.as.listen.url | |
The listen URL is used for direct communication between the members of the metaspace after the discovery process. The listen URL uses this format:
tcp://interface:port/ You can also use an auto-incrementing feature by specifying a range as follows: tcp://interface:Port-[toPort | * ]/ The default value for interface is the first available interface provided by the operating system for the machine. See DataGrid Listen URL for details. The default value for port is the first available port in the 50000+ range. |
|
be.engine.cluster.as.minSeeders | |
TIBCO BusinessEvents sets the value of minimum seeders for user defined spaces to the same value as the quorum size, by default.To override the default value of minimum seeders, you can specify the new value using this property. | |
be.engine.cluster.as.node.retry.times | |
Specifies the number of times TIBCO BusinessEvents retries a put or putAll call on the TIBCO BusinessEvents DataGrid cache. Each retry is done after
5 seconds. The number of retires depends on the Lock Timeout property. To calculate the value for retry times, use the following formula:
retry.times=lock.ttl/5+1 For example, if you set Lock Timeout to 30000, then it is recommended that you set the be.engine.cluster.as.node.retry.times value to 7. |
|
be.engine.cluster.as.shutdown.wait.millis | |
Specifies time (in milliseconds) to wait for the thread that uses ActiveSpaces to complete before shutdown. | |
be.engine.cluster.minCacheServers.strict | |
When this property is set to true and if the number of Cache nodes drops below Quorum, then the cluster is placed into suspend mode. Default value is false. | |
be.engine.cluster.minCacheServers.strict.selfRepair | |
When this property is set to true, the system tries to resume operations if and only when the Quorum is reached again. If this property is set to false once the operations are suspended, then the system will stay in that mode until you manually intervene. Default value is false. | |
be.engine.cluster.quorumCheck.setLenient | |
Using this property, you can change the quorum state behavior. The values are:
The default value is false for inference engines, and true for cache engines. This property can be used at the agent level as well. |
|
be.engine.cluster.cacheNaming.isDescriptive | |
Specifies whether descriptive information (such as dist/repl, unlimited/limited, nobs/bs, and so on) is included in the shared nothing cache names. The values are:
|
|
be.engine.cluster.as.security.mode.role | |
Security role of a node for the secure DataGrid. Possible values are:
Controller or
Requestor.
The Controller is dedicated to enforcing security behavior for a cluster associated with the security domain. Security Controllers are the only discovery nodes in a cluster. The Requestor requires access to the data in the DataGrid, which needs to be authorized by the Controller. A Requestor can never be used as a discovery node. |
|
be.engine.cluster.as.security.file | |
Path to the policy (for controller) or token file (for requestor), which contains the security settings, based on role defined in the be.engine.cluster.as.security.mode.role property. | |
be.engine.cluster.as.security.file.identity.password | |
The password for the identity key in the security policy file or token file specified in be.engine.cluster.as.security.file. | |
be.engine.cluster.as.security.requester.identity.keyfile | |
The absolute path for a file containing the key to use for LDAP with the certificate based authentication. | |
be.engine.cluster.as.security.domain | |
Optional. Domain name for system based user authentication. | |
be.engine.cluster.as.security.username | |
User name for LDAP and system based authentication. | |
be.engine.cluster.as.security.password | |
Password for LDAP and system based authentication. In case authentication type in the policy file is "x509" then this is the password is for the private key in the LDAP identity file specified in be.engine.cluster.as.security.requester.identity.keyfile. | |
be.mm.cluster.as.listen.url | |
If you use well-known-address discovery and TIBCO BusinessEvents Monitoring and Management (MM), you must also add this property at the cluster level of the to-be-monitored project’s CDD file.
Specify the value as the IP of the computer hosting the MM server, and an unused port. See Cluster Discovery and Internal Communication for the procedure, including an additional step you must take. |