You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Ivan Godwin (Jira)" <ji...@apache.org> on 2020/01/09 18:11:00 UTC
[jira] [Updated] (GEODE-7577) Server is not logging about waiting
for missing persistent members
[ https://issues.apache.org/jira/browse/GEODE-7577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ivan Godwin updated GEODE-7577:
-------------------------------
Labels: flaky (was: )
> Server is not logging about waiting for missing persistent members
> ------------------------------------------------------------------
>
> Key: GEODE-7577
> URL: https://issues.apache.org/jira/browse/GEODE-7577
> Project: Geode
> Issue Type: Bug
> Components: persistence
> Reporter: Kirk Lund
> Assignee: Kirk Lund
> Priority: Major
> Labels: flaky
> Fix For: 1.12.0
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> During startup, a Server is supposed to log when it is waiting for missing persistent members. Somehow, this log message is no longer being logged.
> The log message looks like:
> "Region %s has potentially stale data. It is waiting for another member to recover the latest data.%sMy persistent id:%s%s%sMembers with potentially new data:%s%s%sUse the gfsh show missing-disk-stores command to see all disk stores that are being waited on by other members."
> Passing equal numbers into MembershipChangeListener for warningDelay and pollDuration seems to be the main cause.
> I also noticed that the formatting of the message was broken when LocalizedStrings were removed from Geode.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)