geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (GEODE-3026) If a region defining lucene indexes cannot be created, it leaves an AEQ behind
Date Tue, 17 Oct 2017 23:03:00 GMT


ASF subversion and git services commented on GEODE-3026:

Commit 4c13906555f212594cd6c03bf2ea04c4bdd14ae4 in geode's branch refs/heads/feature/GEODE-3026
from [~barry.oglesby]
[;h=4c13906 ]

GEODE-3026: Updated dunit test

> If a region defining lucene indexes cannot be created, it leaves an AEQ behind
> ------------------------------------------------------------------------------
>                 Key: GEODE-3026
>                 URL:
>             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
> 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
> {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(
> 	at org.apache.geode.internal.cache.PartitionedRegion.registerPartitionedRegion(
> 	at org.apache.geode.internal.cache.PartitionedRegion.initPRInternals(
> 	at org.apache.geode.internal.cache.PartitionedRegion.initialize(
> 	at org.apache.geode.internal.cache.GemFireCacheImpl.createVMRegion(
> 	at org.apache.geode.internal.cache.GemFireCacheImpl.basicCreateRegion(
> 	at org.apache.geode.internal.cache.GemFireCacheImpl.createRegion(
> 	at org.apache.geode.cache.RegionFactory.create(
> 	at TestServer.createIndexAndRegionUsingAPI(
> 	at TestServer.main(
> {noformat}
> So, at the end of the GemFireCacheImpl.createVMRegion call, the AEQ exists but the region

This message was sent by Atlassian JIRA

View raw message