Redo log over-commit handling-opracowanie

Redo log over-commit handling. It is possible to control a data node's handling of
operations when too much time is taken flushing redo logs to disk. This occurs when a
given redo log flush takes longer than RedoOverCommitLimit [2246] seconds, more than
RedoOverCommitCounter [2245] times, causing any pending transactions to be aborted. When
this happens, the API node that sent the transaction can handle the operations that should have been
committed either by queuing the operations and re-trying them, or by aborting them, as determined
by DefaultOperationRedoProblemAction [2250]. The data node configuration parameters for
setting the timeout and number of times it may be exceeded before the API node takes this action are
described in the following list:
... zobacz całą notatkę