[jira] [Updated] (GEODE-4173) Destoy entry fails on size calulation in eviction to disk flow
[ https://issues.apache.org/jira/browse/GEODE-4173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Barchak updated GEODE-4173: Summary: Destoy entry fails on size calulation in eviction to disk flow (was: Destoy entry fails in eviction to disk flow ) > Destoy entry fails on size calulation in eviction to disk flow > > > Key: GEODE-4173 > URL: https://issues.apache.org/jira/browse/GEODE-4173 > Project: Geode > Issue Type: Bug > Components: core >Reporter: Igor Barchak > Fix For: 1.3.0 > > > We get exception like below , geode 1.2 and 1.3, while sending load of > destroy requests to entries in a flow where some of them were evicted to > disk > info 2017/12/26 14:45:20.788 IST illin3964-pwinfo1 Processor66> tid=0x178] Unexpected exception during function execution on > local node Partitioned Region > org.apache.geode.InternalGemFireError: Bucket > BucketRegion[path='/__PR/_B__PWINFO__1_8;serial=2943;primary=false] size > (-275) negative after applying delta of -4213 > at Remote Member '10.232.147.91(illin3964-pwinfo2:26687):40008' > in > org.apache.geode.internal.cache.BucketRegion.updateBucketMemoryStats(BucketRegion.java:2294) >at Remote Member '10.232.147.91(illin3964-pwinfo2:26687):40008' in > org.apache.geode.internal.cache.BucketRegion.updateBucket2Size(BucketRegion.java:2282) > at Remote Member '10.232.147.91(illin3964-pwinfo2:26687):40008' > in > org.apache.geode.internal.cache.BucketRegion.updateSizeOnRemove(BucketRegion.java:2154) > at Remote Member '10.232.147.91(illin3964-pwinfo2:26687):40008' > in > org.apache.geode.internal.cache.AbstractRegionMap.destroyEntry(AbstractRegionMap.java:3098) > at Remote Member '10.232.147.91(illin3964-pwinfo2:26687):40008' > in > org.apache.geode.internal.cache.AbstractRegionMap.destroy(AbstractRegionMap.java:1424) > at Remote Member '10.232.147.91(illin3964-pwinfo2:26687):40008' > in > org.apache.geode.internal.cache.LocalRegion.mapDestroy(LocalRegion.java:6452) > at Remote Member '10.232.147.91(illin3964-pwinfo2:26687):40008' > in > org.apache.geode.internal.cache.LocalRegion.mapDestroy(LocalRegion.java:6426) > at Remote Member '10.232.147.91(illin3964-pwinfo2:26687):40008' > in > org.apache.geode.internal.cache.BucketRegion.basicDestroy(BucketRegion.java:1177) > at Remote Member '10.232.147.91(illin3964-pwinfo2:26687):40008' > in > org.apache.geode.internal.cache.DestroyOperation$DestroyMessage.operateOnRegion(DestroyOperation.java:87) > at Remote Member '10.232.147.91(illin3964-pwinfo2:26687):40008' > in > org.apache.geode.internal.cache.DistributedCacheOperation$CacheOperationMessage.basicProcess(DistributedCacheOperation.java:1190) > at Remote Member '10.232.147.91(illin3964-pwinfo2:26687):40008' > in > org.apache.geode.internal.cache.DistributedCacheOperation$CacheOperationMessage.process(DistributedCacheOperation.java:1091) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (GEODE-4173) Destoy entry fails in eviction to disk flow
Igor Barchak created GEODE-4173: --- Summary: Destoy entry fails in eviction to disk flow Key: GEODE-4173 URL: https://issues.apache.org/jira/browse/GEODE-4173 Project: Geode Issue Type: Bug Components: core Reporter: Igor Barchak Fix For: 1.3.0 We get exception like below , geode 1.2 and 1.3, while sending load of destroy requests to entries in a flow where some of them were evicted to disk info 2017/12/26 14:45:20.788 IST illin3964-pwinfo1 tid=0x178] Unexpected exception during function execution on local node Partitioned Region org.apache.geode.InternalGemFireError: Bucket BucketRegion[path='/__PR/_B__PWINFO__1_8;serial=2943;primary=false] size (-275) negative after applying delta of -4213 at Remote Member '10.232.147.91(illin3964-pwinfo2:26687):40008' in org.apache.geode.internal.cache.BucketRegion.updateBucketMemoryStats(BucketRegion.java:2294) at Remote Member '10.232.147.91(illin3964-pwinfo2:26687):40008' in org.apache.geode.internal.cache.BucketRegion.updateBucket2Size(BucketRegion.java:2282) at Remote Member '10.232.147.91(illin3964-pwinfo2:26687):40008' in org.apache.geode.internal.cache.BucketRegion.updateSizeOnRemove(BucketRegion.java:2154) at Remote Member '10.232.147.91(illin3964-pwinfo2:26687):40008' in org.apache.geode.internal.cache.AbstractRegionMap.destroyEntry(AbstractRegionMap.java:3098) at Remote Member '10.232.147.91(illin3964-pwinfo2:26687):40008' in org.apache.geode.internal.cache.AbstractRegionMap.destroy(AbstractRegionMap.java:1424) at Remote Member '10.232.147.91(illin3964-pwinfo2:26687):40008' in org.apache.geode.internal.cache.LocalRegion.mapDestroy(LocalRegion.java:6452) at Remote Member '10.232.147.91(illin3964-pwinfo2:26687):40008' in org.apache.geode.internal.cache.LocalRegion.mapDestroy(LocalRegion.java:6426) at Remote Member '10.232.147.91(illin3964-pwinfo2:26687):40008' in org.apache.geode.internal.cache.BucketRegion.basicDestroy(BucketRegion.java:1177) at Remote Member '10.232.147.91(illin3964-pwinfo2:26687):40008' in org.apache.geode.internal.cache.DestroyOperation$DestroyMessage.operateOnRegion(DestroyOperation.java:87) at Remote Member '10.232.147.91(illin3964-pwinfo2:26687):40008' in org.apache.geode.internal.cache.DistributedCacheOperation$CacheOperationMessage.basicProcess(DistributedCacheOperation.java:1190) at Remote Member '10.232.147.91(illin3964-pwinfo2:26687):40008' in org.apache.geode.internal.cache.DistributedCacheOperation$CacheOperationMessage.process(DistributedCacheOperation.java:1091) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (GEODE-4050) No way from gfsh list members, to find coordinator
[ https://issues.apache.org/jira/browse/GEODE-4050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Barchak resolved GEODE-4050. - Resolution: Duplicate > No way from gfsh list members, to find coordinator > -- > > Key: GEODE-4050 > URL: https://issues.apache.org/jira/browse/GEODE-4050 > Project: Geode > Issue Type: Bug > Components: membership >Reporter: Igor Barchak > Fix For: 1.2.0 > > > No way from gfsh list members, to find coordinator > flag marks preferred coordinators( locators), and not actual current > coordinator -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (GEODE-4098) Mutex guarding buckets statuses container has no timeout hanldling
Igor Barchak created GEODE-4098: --- Summary: Mutex guarding buckets statuses container has no timeout hanldling Key: GEODE-4098 URL: https://issues.apache.org/jira/browse/GEODE-4098 Project: Geode Issue Type: Bug Components: client queues Reporter: Igor Barchak Fix For: 1.2.0 Mutex guarding buckets statuses container has no timeout handling,in ClientMetadataService.cpp Can cause messages stuck on client -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (GEODE-4097) No way to give private fix for geode-core jar
Igor Barchak created GEODE-4097: --- Summary: No way to give private fix for geode-core jar Key: GEODE-4097 URL: https://issues.apache.org/jira/browse/GEODE-4097 Project: Geode Issue Type: Bug Components: management Reporter: Igor Barchak Fix For: 1.3.0 No way to give private fix for geode-core jar in different path , always taken hard coded from %GEODE_HOME/lib -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (GEODE-4050) No way from gfsh list members, to find coordinator
Igor Barchak created GEODE-4050: --- Summary: No way from gfsh list members, to find coordinator Key: GEODE-4050 URL: https://issues.apache.org/jira/browse/GEODE-4050 Project: Geode Issue Type: Bug Components: core Reporter: Igor Barchak Fix For: 1.2.0 No way from gfsh list members, to find coordinator flag marks preferred coordinators( locators), and not actual current coordinator -- This message was sent by Atlassian JIRA (v6.4.14#64029)
