geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (GEODE-4375) Mismatch deserialization of TxCommitMessage
Date Tue, 06 Feb 2018 19:15:00 GMT


ASF subversion and git services commented on GEODE-4375:

Commit 674e729950a6112f6f7a211f3adf22520a420e44 in geode's branch refs/heads/feature/GEODE-3967
from [~bschuchardt]
[;h=674e729 ]

GEODE-4375: Fix problem that an exception occurs when transaction from CacheServer via Pool

Modifying the test for proper backward-compatibility testing

> Mismatch deserialization of TxCommitMessage
> -------------------------------------------
>                 Key: GEODE-4375
>                 URL:
>             Project: Geode
>          Issue Type: Bug
>          Components: serialization, transactions
>            Reporter: Masaki Yamakawa
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.5.0
>          Time Spent: 1h 20m
>  Remaining Estimate: 0h
> I am migrating from GemFire 7.x to Geode. After migration, An exception is now thrown
in transaction commit. I would like to fix this problem.
> There are the following three patterns as a communication of a transaction. In this last
pattern, a deserialization exception is thrown.
> * CacheServer (transaction) -> CacheServer
> * Client (transaction) -> CacheServer
> * CacheServer via Pool (transaction) -> CacheServer
> In toData of TxCommitMessage.RegionCommit.FarSideEntryOp it is decided whether or not
to serialize ShadowKey depending on whether ClientVersion exists or not. In the case of the
last pattern, it is serialized because ClientVersion exists. In fromData case, it decides
whether or not to deserialize by whether it is a Loner or not. In the case of the last pattern,
it is not Loner. As a result, a deserialization exception is thrown.
> Therefore, instead of judging by the internal status of each process, I'd like to send
a flag as to whether ShadowKey exists or not.
> Note: The disadvantage is that bytes are increased slightly.

This message was sent by Atlassian JIRA

View raw message