1.1.1

enforce-unique-host
Boolean that determines whether SQLFire puts redundant copies of the same data in different members
running on the same physical machine. By default, SQLFire tries to put redundant copies on different machines,
Description
but it puts them on the same machine if no other machines are available. Setting this property to true prevents
this and requires different machines for redundant copies.
falseDefault Value
connection (boot)Property Type
gemfire.Prefix
gemfire.DISKSPACE_WARNING_INTERVAL
Configures the frequency (in milliseconds) with which SQLFire logs warning messages for low disk space
conditions. SQLFire logs a low disk space warning in the following situations:
Description
• For a log file directory it logs a warning if the available space is less than 100 MB.
• For a disk store directory it logs a warning if the usable space is less than 1.15 times the space required to
create a new oplog file.
• For the data dictionary directory it logs a warning if the remaining space is less than 50 MB.
10000Default Value
systemProperty Type
n/aPrefix
gemfire.WRITE_LOCK_TIMEOUT
The time to wait before throwing a conflict exception (X0Z02) for a write-write conflict that is detected between two
transactions. If the first transaction that acquired the lock on the conflicting row completes in this period of time (for
Description
example, it commits or aborts) then no conflict occurs. However, keep in mind that SQLFire does not have any built-in
mechanism for detecting distributed deadlocks, so setting this property too high can cause two interlocked transactions
to both block for that period of time. Keep this timeout value small, because increasing the value can have a negative
impact on the overall throughput of a system that has transactions that perform lots of DML. The default value is 0,
which means that the system throws a conflict immediately when it is detected.
If you change this property, set it to the same value on every data store member in your distributed system.
This property configures conflict detection for READ_COMMITTED and REPEATABLE_READ transactions. See
Supported Transaction Isolation Levels on page 152.
0Default Value
systemProperty Type
n/aPrefix
gemfire.READ_LOCK_TIMEOUT
The time to wait before throwing a conflict exception (X0Z02) for a write-read conflict that is detected between two
REPEATABLE_READ transactions. If the read lock acquired by the transaction that has read the conflicting row
Description
completes in this period of time (for example, it commits or aborts) then no conflict occurs for the transaction that is
writing the row. However, keep in mind that SQLFire does not have any built-in mechanism for detecting distributed
deadlocks, so setting this property too high can cause two interlocked transactions to both block for that period of time.
329
Configuration Properties