May 2010 - infinispan-issues - Jboss List Archives

[JBoss JIRA] Resolved: (ISPN-27) RemoteCacheStore, based on delegating to a CacheServer

by Mircea Markus (JIRA)

[ 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 > 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

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (ISPN-458) Tweak for query-cache via hibernate.hbm.xml needed

by Niktia Koksharov (JIRA)

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 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

13 years, 11 months

3
4
0 / 0

[JBoss JIRA] Assigned: (ISPN-31) JPA based cache store

by Manik Surtani (JIRA)

[ https://jira.jboss.org/browse/ISPN-31?page=com.atlassian.jira.plugin.syst... ] Manik Surtani reassigned ISPN-31: --------------------------------- Assignee: Rafael Ribeiro (was: Manik Surtani) > JPA based cache store > --------------------- > > Key: ISPN-31 > URL: https://jira.jboss.org/browse/ISPN-31 > Project: Infinispan > Issue Type: Feature Request > Components: Loaders and Stores > Reporter: Manik Surtani > Assignee: Rafael Ribeiro > Fix For: 5.0.0.BETA1, 5.0.0.Final > > > Store that uses JPA for persistence -- 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

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (ISPN-424) Enhance ping request to take a cache name

by Galder Zamarreno (JIRA)

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 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

13 years, 11 months

1
3
0 / 0

[JBoss JIRA] Updated: (ISPN-180) Colocated nodes should be handled in DIST

by Manik Surtani (JIRA)

[ 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 > 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

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Work stopped: (ISPN-180) Colocated nodes should be handled in DIST

by Manik Surtani (JIRA)

[ 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 > 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

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (ISPN-180) Colocated nodes should be handled in DIST

by Manik Surtani (JIRA)

[ https://jira.jboss.org/browse/ISPN-180?page=com.atlassian.jira.plugin.sys... ] Manik Surtani updated ISPN-180: ------------------------------- JBoss Forum Reference: http://www.mailarchy.com/thread.php?id=473370 Also see email thread. > 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 > 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

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (ISPN-180) Colocated nodes should be handled in DIST

by Manik Surtani (JIRA)

[ 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: 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

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Work started: (ISPN-180) Colocated nodes should be handled in DIST

by Manik Surtani (JIRA)

[ https://jira.jboss.org/browse/ISPN-180?page=com.atlassian.jira.plugin.sys... ] Work on ISPN-180 started 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 > 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

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Commented: (ISPN-180) Colocated nodes should be handled in DIST

by Manik Surtani (JIRA)

[ https://jira.jboss.org/browse/ISPN-180?page=com.atlassian.jira.plugin.sys... ] Manik Surtani commented on ISPN-180: ------------------------------------ See http://community.jboss.org/wiki/DesigningServerHinting for ongoing designs > Colocated nodes should be handled in DIST > ----------------------------------------- > > Key: ISPN-180 > URL: https://jira.jboss.org/browse/ISPN-180 > Project: Infinispan > Issue Type: Feature Request > 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

13 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues May 2010