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

Memory consumption of mirror keep growing in case of drop oldest and distributed transactions when redolog capacity reached

Description

High cpu and memory shortage issues in mirror container when space is configured with drop-oldest policy for mirror and distributed transaction are used when redolog reach its capacity.

Taking several heap dumps its shown that the instances of MultiSourceSingleFileReliableAsyncTargetProcessLog takes more and more memory.
(wait time was configured to 5 seconds, and operations threshold to 1000, but in heap itself more packets are accumulated)

current work around:
configure the space with global order replication
e.g <prop key="cluster-config.groups.group.repl-policy.processing-type">global-order</prop>

Attaching 2 heap dumps of the mirror

Workaround

None

Acceptance Test

None

Status

Assignee

Unassigned

Reporter

Ester Atzmon

Labels

None

Priority

Medium

SalesForce Case ID

11821

Fix versions

None

Commitment Version/s

None

Due date

None

Product

XAP

Edition

Premium

Platform

All