geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anthony Baker (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (GEODE-2526) Enhance log statement in StatsArchiveReader
Date Sat, 17 Jun 2017 18:04:13 GMT

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

Anthony Baker closed GEODE-2526.
--------------------------------

> 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
>             Fix For: 1.2.0
>
>
> 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.4.14#64029)

Mime
View raw message