You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Dan Smith (JIRA)" <ji...@apache.org> on 2016/03/24 19:43:25 UTC
[jira] [Commented] (GEODE-1128) Add log messages and enhance the
output of list-missing-disk-stores to report missing colocated regions
[ https://issues.apache.org/jira/browse/GEODE-1128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15210749#comment-15210749 ]
Dan Smith commented on GEODE-1128:
----------------------------------
The general goal here is that if there are any issues with persistent recovery, they should show up in the log and should also be displayed in list-missing-disk-stores. We might also want to consider logging if there are any unrecovered persistent regions.
> 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
>
> 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)