We're updating the issue view to help you get more done. 

Enhance replication configuration to improve transaction handling

Description

Currently the mirror redo log treats number of regular operations and number of transactions the same.
There are situations which one transaction contains 1000 regular operations, the mirror treats it as one operation only, this can cause any issue with the total size of the redo log calculation.
To solve this kind of situation we should create different configuration parameters for the transactions in addition to the already exist parameters.

Alternatively, we can add weight to replication packets, and make transaction packets weigh as the number of nested operations

Workaround

None

Acceptance Test

SGTest

Status

Assignee

Unassigned

Reporter

Aharon Moll

Priority

Major

Fix versions

Commitment Version/s

12.1

Platform

All

Sprint

None