[
https://issues.apache.org/jira/browse/GEODE-6329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Smith resolved GEODE-6329.
------------------------------
Resolution: Fixed
Fix Version/s: 1.9.0
> gfsh show missing-disk-stores shows disk stores that aren't missing
> -------------------------------------------------------------------
>
> Key: GEODE-6329
> URL: https://issues.apache.org/jira/browse/GEODE-6329
> Project: Geode
> Issue Type: Bug
> Components: management
> Reporter: Dan Smith
> Assignee: Dan Smith
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.9.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> The gfsh show missing-disk-stores command is showing disk stores that aren't
> actually missing.
> To reproduce
> - Start 4 servers with a persistent PR with redundancy 1
> - Stop 2 servers, rebalancing in between
> - Restart the 2 servers and wait for recovery to complete
> Gfsh reports one of the disk stores of the first stopped server as missing.
> There appear to be few problems here. The JMX listMissingDiskStores removes
> disk stores that are reported as present by other members, however the gfsh
> command is not using the same logic, so it's reporting the same disk stores
> as missing even if they are reported as present.
> The JMX command also can fail here, however, because if a member has a disk
> store but 0 buckets, the member is not reporting the disk store as present.
> Finally, the missing disk stores reported by individual nodes come from the
> persistent view of each bucket. Geode should be updating the persistent view
> when each member restarts. Therefore the "missing" disk store should have
> been removed from the persistent view.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
