[ https://jira.jboss.org/browse/ISPN-27?page=com.atlassian.jira.plugin.syst... ]
Mircea Markus resolved ISPN-27.
-------------------------------
Resolution: Done
implemented as an mvn module (./cachestore/remote)
> RemoteCacheStore, based on delegating to a CacheServer
> ------------------------------------------------------
>
> Key: ISPN-27
> URL: https://jira.jboss.org/browse/ISPN-27
> Project: Infinispan
> …
[View More]Issue Type: Feature Request
> Components: Loaders and Stores
> Reporter: Manik Surtani
> Assignee: Mircea Markus
> Priority: Blocker
> Fix For: 4.1.0.CR1, 4.1.0.Final
>
>
> RemoteCacheStore should use the custom binary protocol that is capable of failing over and load balancing. If the backend is configured to use distribution, the same consisitent hashing algorithm should be used by the loader to select the cache server instance in a cluster.
--
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
[View Less]
Tweak for query-cache via hibernate.hbm.xml needed
--------------------------------------------------
Key: ISPN-458
URL: https://jira.jboss.org/browse/ISPN-458
Project: Infinispan
Issue Type: Sub-task
Components: Core API
Affects Versions: 4.0.0.Final
Reporter: Niktia Koksharov
Assignee: Manik Surtani
Priority: Critical
Fix For: 4.1.0.CR1
In current implementation of …
[View More]hibernate-infinispan we can tune only entity and collection settings via hibernate.xml.cfg. But tuning in same way for queries needed too. In current version there are always the same cache region for all queries (look at org.hibernate.cache.infinispan.InfinispanRegionFactory.buildQueryResultsRegion) and it's incorrect.
--
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
[View Less]
Enhance ping request to take a cache name
-----------------------------------------
Key: ISPN-424
URL: https://jira.jboss.org/jira/browse/ISPN-424
Project: Infinispan
Issue Type: Feature Request
Components: Cache Server
Affects Versions: 4.1.0.BETA1
Reporter: Galder Zamarreno
Assignee: Manik Surtani
Priority: Minor
Fix For: 4.1.0.CR1
Enhance Hot Rod ping request to take a …
[View More]cache name so that hash distribution headers can be returned.
Without a cache name, I can't return hashes cos you could easily have multiple caches defined in configuration each with a different consistent hash algorithm.
--
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
[View Less]
[ https://jira.jboss.org/browse/ISPN-180?page=com.atlassian.jira.plugin.sys... ]
Manik Surtani updated ISPN-180:
-------------------------------
Fix Version/s: 5.0.0.BETA1
5.0.0.Final
(was: 4.1.0.Final)
(was: 4.1.0.CR1)
> Colocated nodes should be handled in DIST
> -----------------------------------------
>
> Key: ISPN-180
> URL: https://jira.jboss.org/browse/ISPN-180
> …
[View More] Project: Infinispan
> Issue Type: Feature Request
> Components: Distributed Cache
> Reporter: Manik Surtani
> Assignee: Manik Surtani
> Fix For: 5.0.0.BETA1, 5.0.0.Final
>
>
> DefaultConsistentHash should place addresses on the hash wheel such that colocated nodes are never less than repl_count nodes apart to prevent data loss when a server fails.
--
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
[View Less]
[ https://jira.jboss.org/browse/ISPN-180?page=com.atlassian.jira.plugin.sys... ]
Work on ISPN-180 stopped by Manik Surtani.
> Colocated nodes should be handled in DIST
> -----------------------------------------
>
> Key: ISPN-180
> URL: https://jira.jboss.org/browse/ISPN-180
> Project: Infinispan
> Issue Type: Feature Request
> Components: Distributed Cache
> Reporter: Manik Surtani
> …
[View More] Assignee: Manik Surtani
> Fix For: 5.0.0.BETA1, 5.0.0.Final
>
>
> DefaultConsistentHash should place addresses on the hash wheel such that colocated nodes are never less than repl_count nodes apart to prevent data loss when a server fails.
--
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
[View Less]
[ https://jira.jboss.org/browse/ISPN-180?page=com.atlassian.jira.plugin.sys... ]
Manik Surtani updated ISPN-180:
-------------------------------
Component/s: Distributed Cache
> Colocated nodes should be handled in DIST
> -----------------------------------------
>
> Key: ISPN-180
> URL: https://jira.jboss.org/browse/ISPN-180
> Project: Infinispan
> Issue Type: Feature Request
> Components: …
[View More]Distributed Cache
> Reporter: Manik Surtani
> Assignee: Manik Surtani
> Fix For: 4.1.0.CR1, 4.1.0.Final
>
>
> DefaultConsistentHash should place addresses on the hash wheel such that colocated nodes are never less than repl_count nodes apart to prevent data loss when a server fails.
--
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
[View Less]