You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Darrel Schneider (JIRA)" <ji...@apache.org> on 2019/06/07 23:13:00 UTC
[jira] [Created] (GEODE-6850) Change the Statistics implementation
so that int and longs on the same instance will not have the same id
Darrel Schneider created GEODE-6850:
---------------------------------------
Summary: Change the Statistics implementation so that int and longs on the same instance will not have the same id
Key: GEODE-6850
URL: https://issues.apache.org/jira/browse/GEODE-6850
Project: Geode
Issue Type: Improvement
Components: statistics
Reporter: Darrel Schneider
The current Statistics interface allows stats to be identified with ids of type "int". Currently the first stat that is an 32-bit IntCounter or IntGauge will have an "id" of 0. The same is true of the first 64-bit LongCounter or LongGauge. They both end up with the same id. If you accidently use the id of a 64-bit stat in a api that looks it up as an 32-bit int, then it will be looking at a different stat (the first 32-bit stat instead of the first 64-bit stat).
This overloading of ids becomes even more of a problem when we want to change one from 32-bit to 64-bit.
So instead of overloading ids, the internal implementation should be changed so that each id is unique. I given stat's id should not be used for any other 32-bit or 64-bit stat.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)