[
https://issues.apache.org/jira/browse/GEODE-2526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15889115#comment-15889115
]
ASF subversion and git services commented on GEODE-2526:
--------------------------------------------------------
Commit fb1fdf90198e4767114e32c53c9fc61ceb4c4645 in geode's branch
refs/heads/develop from [~Srikanth Manvi]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=fb1fdf9 ]
GEODE-2526: Enhance log statement to include ResourceTypeName
This closes #406
> Enhance log statement in StatsArchiveReader
> -------------------------------------------
>
> Key: GEODE-2526
> URL: https://issues.apache.org/jira/browse/GEODE-2526
> Project: Geode
> Issue Type: New Feature
> Components: statistics
> Reporter: Srikanth Manvi
> Assignee: Srikanth Manvi
> Priority: Trivial
>
> Rarely stats files are corrupted due to missing ResourceType info in the gfs
> file. In those cases the gfs files cannot be opened in VSD tool as the tool
> throws an error while loading.
> The log statement in the method
> StatsArchiveReader.java(readResourceInstanceCreateToken()) prints out only
> the missing ResourceTypeId which appears to be dynamically created.
> If the log message can be enhanced to include the resourceName as well, it
> will be valuable to know the name of ResourceType that is actually missing in
> the stats file.
> There is a [stats-cleaner | https://github.com/smanvi-pivotal/stats-cleaner]
> utility which takes in a corrupted stats files, name and id of the missing
> ResourceType in the corrupted file and outputs a new .gfs file by filling in
> the missing resource info. The new file can then be loaded and analyzed in
> VSD.
>
> For the [stats-cleaner | https://github.com/smanvi-pivotal/stats-cleaner]
> utility to be usable one needs to know the actual name of missing
> resourceType, hence this New feature request.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
