[JBoss JIRA] (ISPN-5179) Add distributed execution and map/reduce job statistics
by Vladimir Blagojevic (JIRA)
[ https://issues.jboss.org/browse/ISPN-5179?page=com.atlassian.jira.plugin.... ]
Vladimir Blagojevic updated ISPN-5179:
--------------------------------------
Fix Version/s: 7.2.0.Final
(was: 7.1.0.Final)
> Add distributed execution and map/reduce job statistics
> --------------------------------------------------------
>
> Key: ISPN-5179
> URL: https://issues.jboss.org/browse/ISPN-5179
> Project: Infinispan
> Issue Type: Feature Request
> Components: JMX, reporting and management
> Reporter: Vladimir Blagojevic
> Assignee: Vladimir Blagojevic
> Fix For: 7.2.0.Final
>
>
> We should add DMR/JMX statistics for the running distributed execution jobs as well as map/reduce jobs. The statistics will also include overview/total system statistics of previously executed jobs; we might store statistics of individual executed jobs in some internal cache. However, the primary objective is to calculate and maintain dist.exec and map/reduce job statistics for Infinispan admin console.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (ISPN-5179) Add distributed execution and map/reduce job statistics
by Vladimir Blagojevic (JIRA)
Vladimir Blagojevic created ISPN-5179:
-----------------------------------------
Summary: Add distributed execution and map/reduce job statistics
Key: ISPN-5179
URL: https://issues.jboss.org/browse/ISPN-5179
Project: Infinispan
Issue Type: Feature Request
Components: JMX, reporting and management
Reporter: Vladimir Blagojevic
Assignee: Vladimir Blagojevic
Fix For: 7.1.0.Final
We should add DMR/JMX statistics for the running distributed execution jobs as well as map/reduce jobs. The statistics will also include overview/total system statistics of previously executed jobs; we might store statistics of individual executed jobs in some internal cache. However, the primary objective is to calculate and maintain dist.exec and map/reduce job statistics for Infinispan admin console.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (ISPN-3916) Expiration reaper is not enabled until lifespan or max-idle is set
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-3916?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-3916:
-----------------------------------------------
Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1083147|https://bugzilla.redhat.com/show_bug.cgi?id=1083147] from VERIFIED to CLOSED
> Expiration reaper is not enabled until lifespan or max-idle is set
> ------------------------------------------------------------------
>
> Key: ISPN-3916
> URL: https://issues.jboss.org/browse/ISPN-3916
> Project: Infinispan
> Issue Type: Bug
> Components: Server
> Affects Versions: 6.0.1.Final
> Reporter: Wolf-Dieter Fink
> Assignee: Mircea Markus
> Labels: 630
> Fix For: 7.0.0.Alpha1, 7.0.0.Final
>
>
> If a cache is added where entities are with and without expiration by external processes it is expected that the reaper purge the data from memory and datastore.
> As the reaper is only enabled for the cache if the element
> <expiration interval="millis" lifespan="millis" max-idle="millis"/>
> has one of the attributes lifespan or max-idle set to a value >0
> The expired entities will not be removed from the memory or datastore.
> This is an unexpected behaviour and might end in a memory bottleneck if a server is up for a long time.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months