October 2008 - jbosscache-issues - Jboss List Archives

[JBoss JIRA] Created: (JBCACHE-1414) more efficient exists() in JDBCCacheLoader and FileCacheLoader

by Manik Surtani (JIRA)

more efficient exists() in JDBCCacheLoader and FileCacheLoader -------------------------------------------------------------- Key: JBCACHE-1414 URL: https://jira.jboss.org/jira/browse/JBCACHE-1414 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Cache loaders Affects Versions: 2.2.0.GA Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 3.0.0.CR1, 3.0.0.GA, 2.X exists() in both these cache loaders loads the node and then tests if the result is null. Hugely inefficient since it would involve byte stream deserialization. -- 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

16 years, 2 months

1
3
0 / 0

[JBoss JIRA] Commented: (JBCACHE-816) Clustering between data centres

by Galder Zamarreno (JIRA)

[ https://jira.jboss.org/jira/browse/JBCACHE-816?page=com.atlassian.jira.pl... ] Galder Zamarreno commented on JBCACHE-816: ------------------------------------------ Bela Ban - 28/Apr/08 07:06 AM Requirement from JBossCache: all messages a sender S multicasts to the cluster need to be received by S as well, e.g. PREPAREs. (S then simply discards messages sent by itself). > Clustering between data centres > ------------------------------- > > Key: JBCACHE-816 > URL: https://jira.jboss.org/jira/browse/JBCACHE-816 > Project: JBoss Cache > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Clustering > Affects Versions: 1.4.0.GA, 2.0.0.GA > Reporter: Manik Surtani > Assignee: Manik Surtani > Fix For: 3.2.0 > > Original Estimate: 3 weeks > Remaining Estimate: 3 weeks > > This has to do with multiple JBoss Cache clusters deployed on LANs as islands, requiring a bridge between such islands. An ideal use case is where a cluster spans multiple data centres and would need to replicate across a WAN. > The ideal strategy would be to allow for async bridging, since most calls would be colocated to a single LAN, but may fail over to a remote LAN (pretty much the same idea of async repl within a LAN, except that now we treat an entire LAN as a host. Sort of a meta-cluster). > For more details and some brainstorming ideas, see: > http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossCacheAcrossDataCentres -- 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

16 years, 2 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBCACHE-1331) Clustering between data centres

by Galder Zamarreno (JIRA)

[ https://jira.jboss.org/jira/browse/JBCACHE-1331?page=com.atlassian.jira.p... ] Galder Zamarreno resolved JBCACHE-1331. --------------------------------------- Resolution: Duplicate Issue > Clustering between data centres > ------------------------------- > > Key: JBCACHE-1331 > URL: https://jira.jboss.org/jira/browse/JBCACHE-1331 > Project: JBoss Cache > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Replication > Reporter: Manik Surtani > Assignee: Manik Surtani > Fix For: 3.2.0 > > > A mechanism for efficiently replicating state between data centres. -- 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

16 years, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBCACHE-816) Clustering between data centres

by Galder Zamarreno (JIRA)

[ https://jira.jboss.org/jira/browse/JBCACHE-816?page=com.atlassian.jira.pl... ] Galder Zamarreno updated JBCACHE-816: ------------------------------------- Summary: Clustering between data centres (was: Create a CacheProxy to allow cache replication across WANs) Fix Version/s: 3.2.0 (was: 3.1.0) > Clustering between data centres > ------------------------------- > > Key: JBCACHE-816 > URL: https://jira.jboss.org/jira/browse/JBCACHE-816 > Project: JBoss Cache > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Clustering > Affects Versions: 1.4.0.GA, 2.0.0.GA > Reporter: Manik Surtani > Assignee: Manik Surtani > Fix For: 3.2.0 > > Original Estimate: 3 weeks > Remaining Estimate: 3 weeks > > This has to do with multiple JBoss Cache clusters deployed on LANs as islands, requiring a bridge between such islands. An ideal use case is where a cluster spans multiple data centres and would need to replicate across a WAN. > The ideal strategy would be to allow for async bridging, since most calls would be colocated to a single LAN, but may fail over to a remote LAN (pretty much the same idea of async repl within a LAN, except that now we treat an entire LAN as a host. Sort of a meta-cluster). > For more details and some brainstorming ideas, see: > http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossCacheAcrossDataCentres -- 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

16 years, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBCACHE-1348) Use of replication queue and transactions may cause modifications not to be applied on remote nodes

by Manik Surtani (JIRA)

[ https://jira.jboss.org/jira/browse/JBCACHE-1348?page=com.atlassian.jira.p... ] Manik Surtani updated JBCACHE-1348: ----------------------------------- Fix Version/s: (was: 2.X) > Use of replication queue and transactions may cause modifications not to be applied on remote nodes > --------------------------------------------------------------------------------------------------- > > Key: JBCACHE-1348 > URL: https://jira.jboss.org/jira/browse/JBCACHE-1348 > Project: JBoss Cache > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Replication, Transactions > Affects Versions: 2.1.1.GA > Reporter: Manik Surtani > Assignee: Manik Surtani > Priority: Critical > > When prepare method calls are created, they receive a reference to the modification list of the transaction. > On transaction completion, however, the context is cleaned (JBCACHE-1326) which means the modification list is emptied. > This was not a problem in 2.1.0 since 2.1.0 didn't scrub contexts after transaction completion (thus creating a class loader leak - see JBCACHE-1326). -- 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

16 years, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBCACHE-1358) Cache Loader preloading does not happen!

by Manik Surtani (JIRA)

[ https://jira.jboss.org/jira/browse/JBCACHE-1358?page=com.atlassian.jira.p... ] Manik Surtani updated JBCACHE-1358: ----------------------------------- Fix Version/s: (was: 2.X) > Cache Loader preloading does not happen! > ---------------------------------------- > > Key: JBCACHE-1358 > URL: https://jira.jboss.org/jira/browse/JBCACHE-1358 > Project: JBoss Cache > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Cache loaders > Affects Versions: 2.1.0.GA, 2.1.1.GA > Reporter: Manik Surtani > Assignee: Manik Surtani > Priority: Critical > Fix For: 2.2.0.GA > > > Regression on preloading. Cache loader tests appear not to test preloading anymore either. -- 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

16 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosscache-issues October 2008