1. /
  2. Security Response/
  3. Glossary/
  4. latency protection

Glossary

A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z | _1234567890

latency protection

For RLINKs operating in asynchronous mode, which may fall behind, the latency protection attribute (<code>latencyprot</code>) of the RLINK is used to limit the maximum number of outstanding write requests. The maximum number of outstanding write requests cannot exceed the value set in <code>latency_high_mark</code>, and cannot increase until the number of outstanding writes falls to the <code>latency_low_mark</code>.

For RLINKs operating in asynchronous mode, which may fall behind, the latency protection attribute (<code>latencyprot</code>) of the RLINK is used to limit the maximum number of outstanding write requests. The maximum number of outstanding write requests cannot exceed the value set in <code>latency_high_mark</code>, and cannot increase until the number of outstanding writes falls to the <code>latency_low_mark</code>.

The method to ensure that the Secondary node does not fall too far behind in updating the data from the Primary node, when replicating in the asynchronous mode. This is done by setting the two limit values called the Latency_high_mark and the Latency_low_mark.