1.0

Table Of Contents
Keep this value small. The default value is 0, which means that the system throws a conict for the writer immediately
on detection during commit.
If you change this property, set it to the same value on every data store member in your distributed system.
This property congures conict detection for READ_COMMITTED and REPEATABLE_READ transactions. See
Supported Transaction Isolation Levels on page 138.
0Default Value
systemProperty Type
n/aPrex
gemfire.LOCK_MAX_TIMEOUT
This is the maximum time to wait for a transaction that is committing a row that the current transaction is trying
to read or write. Do not change this property unless transactions involve a large number of writes and potentially
can take a very long time during commit to write to datastores. The default is 5 minutes.
If you change this property, set it to the same value on every data store member in your distributed system.
Description
This property congures conict detection for READ_COMMITTED and REPEATABLE_READ transactions.
See Supported Transaction Isolation Levels on page 138.
5Default Value
systemProperty Type
n/aPrex
gemfire.tx-disable-batching
Boolean that determines whether SQLFire detects conicts in thin client transactions lazily or at operation time. With
the default value of "false," SQLFire detects any conicts in DML operations lazily. DML conicts may be thrown
Description
by the system at some point later in the transaction (for example, even when executing queries or at commit time).
Set this option to "true" on all data store members in your distributed system to immediately detect conicts at operation
time for thin clients.
Note: Enabling gemfire.tx-disable-batching can degrade performance signicantly.
Enable this option only after you have thoroughly tested the setting in your system, and you have determined
that the performance tradeoff is necessary to provide immediate conict detection with thin clients.
falseDefault Value
systemProperty Type
n/aPrex
host-data
Species whether this SQLFire member will host table data.
Setting this value to false boots a SQLFire accessor member with the full SQLFire engine. The accessor (or peer
client) participates in routing queries to other members, but it does not host replicated or partitioned data, and it does
not persist the data dictionary.
Description
309
Configuration Properties