geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kenneth Howe (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (GEODE-1128) Add log messages and enhance the output of list-missing-disk-stores to report missing colocated regions
Date Mon, 25 Jul 2016 17:42:20 GMT

     [ https://issues.apache.org/jira/browse/GEODE-1128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kenneth Howe updated GEODE-1128:
--------------------------------

I sent the following proposal to the geode-dev list for a discussion on dealing with one possible
missing colocated child region scenario.

I’d like to propose a functional change to cache creation when a cache server is created
via a cache.xml file. This proposal originated from work on GEODE-1128 dealing with missing
colocated regions. The change is to fail cache creation if there are missing colocated regions
in the cache.xml that will prevent persistent PR recovery.

Discussion:
When persistent PRs are colocated, the parent region is created first, but persistent data
recovery isn’t done until all the colocated regions have been created. Currently, if a child
region is not created, the cache creation will succeed but persistent data is not recovered.
This is the condition reported in the Jira ticket

When caches and regions are created via the APIs, or interactively with gfsh, the cache is
created, then the parent region(s), then the child region(s). There will always be an unknown
delay between each of these steps. The parent region creation succeeds, but internally Geode
does not know when (or if) the child regions will be created. Normally the child regions are
created after a short period and recovery proceeds, so the parent region having unrecovered
data is a transitory state. If the child region is not created, the the parent region data
will not be recovered. In this case a warning can be logged if the missing child regions aren’t
created within a reasonable time. 

However, when the cache creation is done via a cache.xml file, regions are created as part
of the cache creation. In this case it’s known fairly quickly that there’s a misconfiguration
that will prevent persistent PR recovery. The cache creation can be failed immediately alerting
the user to the misconfiguration.


> Add log messages and enhance the output of list-missing-disk-stores to report missing
colocated regions
> -------------------------------------------------------------------------------------------------------
>
>                 Key: GEODE-1128
>                 URL: https://issues.apache.org/jira/browse/GEODE-1128
>             Project: Geode
>          Issue Type: Bug
>          Components: persistence
>            Reporter: Dan Smith
>            Assignee: Kenneth Howe
>
> Persistent recovery waits until all colocated regions are created. This is necessary
in order to maintain colocation. However, it can result in surprising behavior if a user doesn't
create a region or, in the case of GEODE-1117, geode doesn't create an internal region.
> We need a warning level log message indicating that some colocated regions are missing.
We do have a log message after 15 seconds if other members have not created persistent regions
- see the code in RedundancyLogger.logWaitingForMembers.
> We should enhance the logger to report any missing colocated regions as well.
> The list-missing-disk-stores command should also be enhanced to report missing colocated
regions



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message