You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Alexander Murmann (Jira)" <ji...@apache.org> on 2022/08/23 07:10:00 UTC
[jira] [Updated] (GEODE-10410) Rebalance Guard Prevent Lost Bucket Recovery
[ https://issues.apache.org/jira/browse/GEODE-10410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexander Murmann updated GEODE-10410:
--------------------------------------
Labels: needsTriage (was: )
> Rebalance Guard Prevent Lost Bucket Recovery
> --------------------------------------------
>
> Key: GEODE-10410
> URL: https://issues.apache.org/jira/browse/GEODE-10410
> Project: Geode
> Issue Type: Bug
> Reporter: Weijie Xu
> Priority: Major
> Labels: needsTriage
>
> Following steps reproduce the issue:
> Run the start.gfsh in the attached example, which configures a geode system with a partitioned region and a gateway sender. So there are two regions, the manually created region, and the queue region.
> Then run the example code, which will source ~400M data and 5 times amount of events into the system. All data are sourced into the system, no bucket lost, and no out of memory.
> Then stop one of the server, and revoke the disk file of the server.
> Then start the server, which will trigger a bucket recovery. After that, there will be part of secondary bucket lost.
> gfsh>show metrics --region=/example-region
> | numBucketsWithoutRedundancy | 63
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)