[JBoss JIRA] (ISPN-6340) Expose indexing statistics via DMR
by Adrian Nistor (JIRA)
[ https://issues.jboss.org/browse/ISPN-6340?page=com.atlassian.jira.plugin.... ]
Adrian Nistor updated ISPN-6340:
--------------------------------
Description: It would be great to have status about progress and size of the index as well! Is index in healthy, is it broken, does it need rebuilding? (was: It would be great to have status about progress and size of the index as well! Is index in healthy, is it brojen, does it need rebuilding?)
> Expose indexing statistics via DMR
> ----------------------------------
>
> Key: ISPN-6340
> URL: https://issues.jboss.org/browse/ISPN-6340
> Project: Infinispan
> Issue Type: Feature Request
> Components: JMX, reporting and management
> Reporter: Adrian Nistor
> Assignee: Gustavo Fernandes
> Fix For: 9.0.0.Beta1, 9.0.0.Final
>
>
> It would be great to have status about progress and size of the index as well! Is index in healthy, is it broken, does it need rebuilding?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 1 month
[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 closed ISPN-5179.
-------------------------------------
Resolution: Won't Do
> 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: 9.0.0.Beta1
>
>
> 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
(v7.2.3#72005)
8 years, 1 month
[JBoss JIRA] (ISPN-6340) Expose indexing statistics via DMR
by Vladimir Blagojevic (JIRA)
[ https://issues.jboss.org/browse/ISPN-6340?page=com.atlassian.jira.plugin.... ]
Vladimir Blagojevic updated ISPN-6340:
--------------------------------------
Description: It would be great to have status about progress and size of the index as well! Is index in healthy, is it brojen, does it need rebuilding?
> Expose indexing statistics via DMR
> ----------------------------------
>
> Key: ISPN-6340
> URL: https://issues.jboss.org/browse/ISPN-6340
> Project: Infinispan
> Issue Type: Feature Request
> Components: JMX, reporting and management
> Reporter: Adrian Nistor
> Assignee: Gustavo Fernandes
> Fix For: 9.0.0.Beta1, 9.0.0.Final
>
>
> It would be great to have status about progress and size of the index as well! Is index in healthy, is it brojen, does it need rebuilding?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 1 month
[JBoss JIRA] (ISPN-6346) Zipkin based cluster-wide request tracing
by Vladimir Blagojevic (JIRA)
[ https://issues.jboss.org/browse/ISPN-6346?page=com.atlassian.jira.plugin.... ]
Vladimir Blagojevic updated ISPN-6346:
--------------------------------------
Priority: Minor (was: Major)
> Zipkin based cluster-wide request tracing
> -----------------------------------------
>
> Key: ISPN-6346
> URL: https://issues.jboss.org/browse/ISPN-6346
> Project: Infinispan
> Issue Type: Feature Request
> Components: JMX, reporting and management
> Reporter: Galder Zamarreño
> Assignee: Galder Zamarreño
> Priority: Minor
> Fix For: 9.0.0.Final
>
>
> Zipkin (http://zipkin.io) is a distributed tracing system that started at Twitter.
> Infinispan should integrate with it so that we can trace individual cache requests in terms of which components it touches and how long it takes in each, and also when the cache requests end up going to other nodes (plus see which remote components it touches).
> The idea is that this should give us a better idea of what a particular operation does in terms of how many nodes it goes to, and what it does in each. This would be hugely beneficial to be able to better analyse performance issues.
> A key advantage of Zipkin is that it can be run in production since it can be configured to only track a fraction of all requests, making it even more valuable from the monitoring POV.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 1 month
[JBoss JIRA] (ISPN-7205) Query DSL should not require the use of toBuilder() method to switch context
by Adrian Nistor (JIRA)
Adrian Nistor created ISPN-7205:
-----------------------------------
Summary: Query DSL should not require the use of toBuilder() method to switch context
Key: ISPN-7205
URL: https://issues.jboss.org/browse/ISPN-7205
Project: Infinispan
Issue Type: Enhancement
Reporter: Adrian Nistor
Assignee: Adrian Nistor
Fix For: 9.0.0.Beta1, 9.0.0.Final
After completing a 'having' filter condition we need to call toBuilder() in order to move from FilterConditionContext to QueryBuilder context to be able to finalize the constuction and invoke build().
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 1 month