Bug 1016450 - Cache statistics update differently in library and Client-Server mode
Summary: Cache statistics update differently in library and Client-Server mode
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Data Grid 6
Classification: JBoss
Component: Infinispan
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ER3
: 6.5.0
Assignee: Vladimir Blagojevic
QA Contact: Martin Gencur
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-08 08:15 UTC by Jiri Holusa
Modified: 2015-06-23 12:24 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-23 12:24:57 UTC
Type: Bug


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker ISPN-3602 0 Minor Resolved Cache statistics update differently in library and Client-Server mode 2015-05-04 06:51:55 UTC

Description Jiri Holusa 2013-10-08 08:15:29 UTC
When running jdg quickstart carmart ( https://github.com/infinispan/jdg-quickstart/tree/master/carmart ) I noticed interesting thing.

When calling replace() in library mode, the number of stores in cache statistics doesn't change whereas when calling in Client-Server mode, the number of stores increase by 1.

I went deeper into the code and I found out that in CacheMgmtInterceptor, where there are implemented methods for such statistics updates (like for put() ), there isn't implemented method for updating stats for replace() method, so the control flow is just passed.

I think it should be consistent, but I don't know which approach is intended, if either increase by 1 or leave it the same.

If increase is the answer than the solution is simple, implement CacheMgmtInterceptor.visitReplaceCommand(...) the same way as e.g. visitPutKeyValueCommand.

Comment 2 JBoss JIRA Server 2015-01-12 11:22:26 UTC
Tristan Tarrant <ttarrant> updated the status of jira ISPN-3602 to Resolved


Note You need to log in before you can comment on or make changes to this bug.