[infinispan-issues] [JBoss JIRA] (ISPN-1967) Expose CacheView string via JMX
[
https://issues.jboss.org/browse/ISPN-1967?page=com.atlassian.jira.plugin....
]
Michal Linhard commented on ISPN-1967:
--------------------------------------
Now I'm using attribute "View" at
jgroups:type=channel,cluster="default"
So for example, would be nice to have something like "PendingView" and
"CommitedView" at
jboss.infinispan:type=Cache,name="testCache(dist_sync)",manager="default",component=DistributedStateTransferManager
Is such thing feasible ?
Expose CacheView string via JMX
-------------------------------
Key: ISPN-1967
URL: https://issues.jboss.org/browse/ISPN-1967
Project: Infinispan
Issue Type: Feature Request
Components: JMX, reporting and management
Affects Versions: 5.1.3.FINAL
Reporter: Michal Linhard
Assignee: Manik Surtani
The JGroups view and CacheView differs and this causes trouble finding out what state the
CacheView is in during elasticity/reslience tests.
My test controller is driven by JGroups view, there was this particular case where this
lead to test failure, or better said wrongly controlled test.
After node0002 was killed in view 7:
http://www.qa.jboss.com/~mlinhard/hyperion/run53-elas-dist-basic/table.html
the controller saw JGroups view: [node0003/default|5] [node0003/default,
node0004/default]
which maybe existed in JGroups layer but never in Infinispan - in infinispan there was
partition {node0003} + {node0004}
and therefore it went on with the test which lead to errors, among others ISPN-1965,
might be caused by this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira