[
https://issues.apache.org/jira/browse/GEODE-4769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16534920#comment-16534920
]
Vadim Lotarev commented on GEODE-4769:
--------------------------------------
Does this fix mean that all entries are _always_ stored in serialized form now
in the local cache? So in order to get them deserialization is always
performed? Don't you think that this will affect cache performance? One of
advantages of Geode was the fact that it worked with the local cache really
fast because data were stored in not serialized form most of the time ...
> Serialize region entry before putting in local cache
> ----------------------------------------------------
>
> Key: GEODE-4769
> URL: https://issues.apache.org/jira/browse/GEODE-4769
> Project: Geode
> Issue Type: Improvement
> Components: regions
> Reporter: Kirk Lund
> Assignee: Kirk Lund
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.6.0
>
> Time Spent: 2h 20m
> Remaining Estimate: 0h
>
> This will prevent cache inconsistency when dealing with key or value objects
> that have broken serialization.
> Test should create two members with a REPLICATE region. If one member
> performs a put, but the serialization fails then the region entry currently
> ends up existing in only the cache of the member that performed the put
> locally. The change will prevent this from occurring.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
