[JBoss JIRA] (ISPN-5234) Implement single cluster view page (P1)
by Pedro Ruivo (JIRA)
[ https://issues.jboss.org/browse/ISPN-5234?page=com.atlassian.jira.plugin.... ]
Pedro Ruivo updated ISPN-5234:
------------------------------
Fix Version/s: 8.1.0.Final
(was: 8.0.0.Final)
> Implement single cluster view page (P1)
> ---------------------------------------
>
> Key: ISPN-5234
> URL: https://issues.jboss.org/browse/ISPN-5234
> Project: Infinispan
> Issue Type: Task
> Components: JMX, reporting and management
> Reporter: Vladimir Blagojevic
> Assignee: Vladimir Blagojevic
> Fix For: 8.1.0.Final
>
>
> In our admin console current single cluster view page does not contain the following functionality that should be implemented:
> * -Zoom in/out-
> * Node availability/detail
> * Filter by metrics (node view)
> * Filter by metrics (cache view)
> * Search node (search as you type)
> * Search cache (search as you type)
> * -Cluster switcher-
> * Cluster status view
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 7 months
[JBoss JIRA] (ISPN-5210) Support writing multiple modifications to cache stores in batch when using Transactions
by Pedro Ruivo (JIRA)
[ https://issues.jboss.org/browse/ISPN-5210?page=com.atlassian.jira.plugin.... ]
Pedro Ruivo updated ISPN-5210:
------------------------------
Fix Version/s: 8.1.0.Final
(was: 8.0.0.Final)
> Support writing multiple modifications to cache stores in batch when using Transactions
> ---------------------------------------------------------------------------------------
>
> Key: ISPN-5210
> URL: https://issues.jboss.org/browse/ISPN-5210
> Project: Infinispan
> Issue Type: Feature Request
> Components: Loaders and Stores
> Affects Versions: 6.0.2.Final, 7.1.0.Final
> Reporter: Richard Lucas
> Fix For: 8.1.0.Final
>
>
> Currently writes to a cache store are performed individually for each modification to the cache.
> While this makes sense when using a non-tx cache it would be beneficial to support writing multiple modifications to a cache store in a single call when using a Tx cache.
> Currently all writes are performed in the commit phase and are done by looping through the modifications in the Tx and writing each one in turn to the the store.
> Instead of doing this it would useful to pass all modifications to the store in a single call, this would allow:
> a) Taking advantage of support for batch updates in underlying stores (JDBC, MongoDB, DynamoDB) for a more efficient write through.
> b) Allow store implementations the chance to clean up if one or more updates in the batch fail (this is especially useful if the store does not support Tx and rollbacks as it means the store implementation can at least try to clean up any partial updates it has performed, something which is not currently possible).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 7 months
[JBoss JIRA] (ISPN-5179) Add distributed execution and map/reduce job statistics
by Pedro Ruivo (JIRA)
[ https://issues.jboss.org/browse/ISPN-5179?page=com.atlassian.jira.plugin.... ]
Pedro Ruivo updated ISPN-5179:
------------------------------
Fix Version/s: 8.1.0.Final
(was: 8.0.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: 8.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.15#6346)
8 years, 7 months
[JBoss JIRA] (ISPN-5163) A write operation with the SKIP_LOCKING flag can roll back the transaction
by Pedro Ruivo (JIRA)
[ https://issues.jboss.org/browse/ISPN-5163?page=com.atlassian.jira.plugin.... ]
Pedro Ruivo updated ISPN-5163:
------------------------------
Fix Version/s: 8.1.0.Final
(was: 8.0.0.Final)
> A write operation with the SKIP_LOCKING flag can roll back the transaction
> --------------------------------------------------------------------------
>
> Key: ISPN-5163
> URL: https://issues.jboss.org/browse/ISPN-5163
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 7.0.3.Final, 7.1.0.Beta1
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Fix For: 8.1.0.Final
>
>
> When a write operation has the SKIP_LOCKING flag, it does not send a {{LockControlCommand}} to the primary owner, but it can send a {{ClusteredGetCommand}} with {{acquireRemoteLocks=true}} instead. The {{ClusteredGetCommmand}} will then execute a {{LockControlCommand}} with the origin not set properly, and {{TxInterceptor}} will roll back the transaction because the originator ({{null}}) appears to have left the cluster.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 7 months
[JBoss JIRA] (ISPN-5427) Change getAll to return ordered map
by Pedro Ruivo (JIRA)
[ https://issues.jboss.org/browse/ISPN-5427?page=com.atlassian.jira.plugin.... ]
Pedro Ruivo updated ISPN-5427:
------------------------------
Fix Version/s: 8.1.0.Final
(was: 8.0.0.Final)
> Change getAll to return ordered map
> -----------------------------------
>
> Key: ISPN-5427
> URL: https://issues.jboss.org/browse/ISPN-5427
> Project: Infinispan
> Issue Type: Enhancement
> Components: Core, Remote Protocols
> Reporter: William Burns
> Assignee: William Burns
> Fix For: 8.1.0.Final
>
>
> Currently our getAll returns a map of entries that exist in the cache in any order. We could enhance this to return a map where the entries are in the same iteration order of the Set (important when the user uses a LinkedHashSet). We could even do something like List<V> getAll(List<K>) to show better ordering as an option too.
> This has 2 immediate advantages.
> 1. Remote getAll no longer requires to serialize all the keys in the response since it knows which values map to which keys based on what it sent.
> 2. Query results need ordered List as well. See query/src/main/java/org/infinispan/query/impl/EntityLoader.java
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
8 years, 7 months