[
https://issues.apache.org/jira/browse/GEODE-9625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17428381#comment-17428381
]
ASF subversion and git services commented on GEODE-9625:
--------------------------------------------------------
Commit 3a7b7bae47b454b8c9f47f80be3a0a90a4877343 in geode's branch
refs/heads/support/1.14 from Jacob Barrett
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=3a7b7ba ]
GEODE-9625: Only serialize transaction metadata when grouping enabled. (#6984)
(cherry picked from commit ab651eba9558752fe1336919e462350f4581a22a)
> GatwaySenderEventImpl always serializes metadata necessary only for
> transaction grouping
> ----------------------------------------------------------------------------------------
>
> Key: GEODE-9625
> URL: https://issues.apache.org/jira/browse/GEODE-9625
> Project: Geode
> Issue Type: Bug
> Components: wan
> Affects Versions: 1.14.0, 1.15.0
> Reporter: Jacob Barrett
> Assignee: Jacob Barrett
> Priority: Major
> Labels: blocks-1.14.1, pull-request-available
> Fix For: 1.14.1, 1.15.0
>
>
> Recent additions for transaction grouping in WAN caused
> GatewaySenderEventImpl to serialize transaction ID and last transaction flags
> for every event regardless of the configuration of the transaction grouping
> option. This results in both WAN and AEQ queues to replication unnecessary
> data. Transaction ID also includes the member ID which is a large-sh object.
> The overhead should be removed from queues that don't need that metadata.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
