Ability to manage cluster-wide configuration via a central management console
-----------------------------------------------------------------------------
Key: ISPN-129
URL: https://jira.jboss.org/jira/browse/ISPN-129
Project: Infinispan
Issue Type: Feature Request
Components: JMX, reporting and management
Reporter: Manik Surtani
Assignee: Manik Surtani
Fix For: 5.0.0.GA
Perhaps a lightweight form of JBoss AS' profile service, or something similar.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Ability to bring up/take down nodes based on SLAs
-------------------------------------------------
Key: ISPN-127
URL: https://jira.jboss.org/jira/browse/ISPN-127
Project: Infinispan
Issue Type: Feature Request
Components: JMX and reporting
Reporter: Manik Surtani
Assignee: Manik Surtani
Fix For: 4.1.0.GA
Need to look at what JOPR can provide by way of bringing up or killing instances based on overall load. Perhaps other metrics such as time of day could be used as well. Would be very useful to help build out a truly 'elastic' data grid.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Management console to graph nodes visually
------------------------------------------
Key: ISPN-126
URL: https://jira.jboss.org/jira/browse/ISPN-126
Project: Infinispan
Issue Type: Feature Request
Components: JMX and reporting
Reporter: Manik Surtani
Assignee: Manik Surtani
Fix For: 4.1.0.GA
This should also include colour coded visuals to report activity, status, health etc. Need to investigate what JOPR can provide here, via the agent.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Create a cache store to work with GAE/J's JPA implementation
------------------------------------------------------------
Key: ISPN-121
URL: https://jira.jboss.org/jira/browse/ISPN-121
Project: Infinispan
Issue Type: Feature Request
Components: Loaders and Stores
Reporter: Manik Surtani
Assignee: Manik Surtani
Fix For: 4.1.0.BETA1, 4.1.0.GA
A cache store that could store state on Google AppEngine for Java's JPA backend.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Inform the wider community about Spring INFINISPAN
--------------------------------------------------
Key: ISPN-1030
URL: https://issues.jboss.org/browse/ISPN-1030
Project: Infinispan
Issue Type: Sub-task
Reporter: Olaf Bergner
Assignee: Manik Surtani
We need to tell the community about Spring INFINISPAN, what it is good for, how it is to be used. This should comprise
* providing a sample application,
* blogging about it and
* document it in our wiki.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
With L1 disabled a new node join may result some entries are not invalidated for non-owner in DIST mode
-------------------------------------------------------------------------------------------------------
Key: ISPN-1012
URL: https://issues.jboss.org/browse/ISPN-1012
Project: Infinispan
Issue Type: Bug
Affects Versions: 4.2.1.FINAL
Reporter: Changgeng Li
Assignee: Manik Surtani
I have a test case that have 30,000 entries in cache in dist mode with number of owner set to 2 and L1 is disabled. A new node join the cluster, then the total number of entries in all cache is larger than 60,000. Even worse, after I execute cache.clear() on all caches in the cluster, there are still lots of entries left.
The attached unit test can reproduce this issue.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
FileCacheStore should use fsync() when writing to disk
------------------------------------------------------
Key: ISPN-979
URL: https://issues.jboss.org/browse/ISPN-979
Project: Infinispan
Issue Type: Feature Request
Components: Loaders and Stores
Affects Versions: 4.2.0.Final
Reporter: Manik Surtani
Assignee: Manik Surtani
Fix For: 4.2.1.FINAL
This would be an optional flag, offering one of 3 modes (no sync, periodic sync - e.g., every second - and sync per write).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Replace CacheEntryEvictedEvent with CacheEntriesEvictedEvent (note the plural)
------------------------------------------------------------------------------
Key: ISPN-720
URL: https://jira.jboss.org/browse/ISPN-720
Project: Infinispan
Issue Type: Task
Components: Core API
Affects Versions: 4.2.0.Final
Reporter: Trustin Lee
Assignee: Trustin Lee
Fix For: 5.0.0.BETA1
CacheEntryEvictedEvent should be replaced with CacheEntriesEvictedEvent to fully utilize the improvements in EvictionListener (see ISPN-718).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira