You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2017/10/12 21:56:00 UTC
[jira] [Commented] (GEODE-3026) If a region defining lucene indexes
cannot be created, it leaves an AEQ behind
[ https://issues.apache.org/jira/browse/GEODE-3026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16202687#comment-16202687 ]
ASF subversion and git services commented on GEODE-3026:
--------------------------------------------------------
Commit 25fbf88b21990e892f91fec31e34ecb55d4c2dcb in geode's branch refs/heads/feature/GEODE-3026 from [~barry.oglesby]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=25fbf88 ]
GEODE-3026: Renamed RegionService to RegionCacheService
> If a region defining lucene indexes cannot be created, it leaves an AEQ behind
> ------------------------------------------------------------------------------
>
> Key: GEODE-3026
> URL: https://issues.apache.org/jira/browse/GEODE-3026
> Project: Geode
> Issue Type: Bug
> Components: lucene
> Reporter: Barry Oglesby
>
> This is ok if the member is started with xml, because it will fail to start, but if the region is attempted to be created using java API or gfsh, then the server will be in an inconsistent state.
> It will have defined the AEQ like:
> {noformat}
> [info 2017/06/02 13:02:15.047 PDT <main> tid=0x1] Started ParallelGatewaySender{id=AsyncEventQueue_full_index#_data,remoteDsId=-1,isRunning =true}
> {noformat}
> But will fail to create the region (in this case I created the region with a different number of buckets):
> {noformat}
> [warning 2017/06/02 13:02:15.126 PDT <main> tid=0x1] Initialization failed for Region /data
> java.lang.IllegalStateException: The total number of buckets found in PartitionAttributes ( 16 ) is incompatible with the total number of buckets used by other distributed members. Set the number of buckets to 66
> at org.apache.geode.internal.cache.PartitionRegionConfigValidator.validatePartitionAttrsFromPRConfig(PartitionRegionConfigValidator.java:102)
> at org.apache.geode.internal.cache.PartitionedRegion.registerPartitionedRegion(PartitionedRegion.java:1337)
> at org.apache.geode.internal.cache.PartitionedRegion.initPRInternals(PartitionedRegion.java:987)
> at org.apache.geode.internal.cache.PartitionedRegion.initialize(PartitionedRegion.java:1157)
> at org.apache.geode.internal.cache.GemFireCacheImpl.createVMRegion(GemFireCacheImpl.java:3104)
> at org.apache.geode.internal.cache.GemFireCacheImpl.basicCreateRegion(GemFireCacheImpl.java:3004)
> at org.apache.geode.internal.cache.GemFireCacheImpl.createRegion(GemFireCacheImpl.java:2992)
> at org.apache.geode.cache.RegionFactory.create(RegionFactory.java:758)
> at TestServer.createIndexAndRegionUsingAPI(TestServer.java:104)
> at TestServer.main(TestServer.java:47)
> {noformat}
> So, at the end of the GemFireCacheImpl.createVMRegion call, the AEQ exists but the region doesn't.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)