You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geode.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2016/12/12 22:36:59 UTC
[jira] [Commented] (GEODE-2129) Need to generate pdx type id
random(or avoid sequential)
[ https://issues.apache.org/jira/browse/GEODE-2129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15743375#comment-15743375 ]
ASF subversion and git services commented on GEODE-2129:
--------------------------------------------------------
Commit b04227117bbcc7d28473ad0e3743baa5e54bc022 in geode's branch refs/heads/feature/GEODE-1930 from [~hitesh.khamesra]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=b042271 ]
GEODE-2129 Make pdxType id random.
Right now pdxtype id has 4 bytes. Out of those 4 bytes, one byte
reserved for distributed-system-id, this make sure type id generated
from different cluster has different id. For rest of the three bytes we
just increment counter to create new pdxtype id. In the field, we have
observed that sometimes this pdxType Id collides. One reason could be
they end up having same distributed-system-id for the different cluster.
Thus to avoid a collision, we will be using hashcode of pdxType for
three bytes of pdxType id. That will reduce the possibility of
collision.
Apart from that changed getOldValue call to region.get in
PeerTypeRegistration.
updated
updated
updated
update
> Need to generate pdx type id random(or avoid sequential)
> --------------------------------------------------------
>
> Key: GEODE-2129
> URL: https://issues.apache.org/jira/browse/GEODE-2129
> Project: Geode
> Issue Type: Bug
> Components: serialization
> Reporter: Hitesh Khamesra
> Assignee: Hitesh Khamesra
>
> Right now pdxtype id has 4 bytes. Out of those 4 bytes, one byte reserved for distributed-system-id, this make sure type id generated from different cluster has different id. For rest of the three bytes we just increment counter to create new pdxtype id. In the field, we have observed that sometimes this pdxType Id collides. One reason could be they end up having same distributed-system-id for the different cluster.
> Thus to avoid a collision, we will be using hashcode of pdxType for three bytes of pdxType id. That will reduce the possibility of collision.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)