June 2011 - infinispan-issues - Jboss List Archives

[JBoss JIRA] Created: (ISPN-916) Reducing network calls on get in Distribution mode

by Sudheer Krishna (JIRA)

Reducing network calls on get in Distribution mode -------------------------------------------------- Key: ISPN-916 URL: https://issues.jboss.org/browse/ISPN-916 Project: Infinispan Issue Type: Enhancement Affects Versions: 4.2.0.Final Reporter: Sudheer Krishna Assignee: Manik Surtani Priority: Optional A get call made in distribution mode - make num-copies remote calls paralelly(when data is not present locally). Can there be a configuration option provided to make a single call instead. this is just an enhancement to reduce network calls if possible. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

2
3
0 / 0

[JBoss JIRA] Updated: (ISPN-20) check whether locking in JDBC cache stores can be replaced with SELECT FOR UPDATE

by Manik Surtani (JIRA)

[ https://issues.jboss.org/browse/ISPN-20?page=com.atlassian.jira.plugin.sy... ] Manik Surtani updated ISPN-20: ------------------------------ Fix Version/s: 5.2.0.Final (was: 5.1.0.BETA1) (was: 5.1.0.Final) > check whether locking in JDBC cache stores can be replaced with SELECT FOR UPDATE > --------------------------------------------------------------------------------- > > Key: ISPN-20 > URL: https://issues.jboss.org/browse/ISPN-20 > Project: Infinispan > Issue Type: Feature Request > Components: Loaders and Stores, Locking and Concurrency > Reporter: Mircea Markus > Assignee: Mircea Markus > Labels: hackathon > Fix For: 5.1.0.BETA1, 5.1.0.Final > > > Not sure whether the 'outside' locking (MVCC) can't be used so that we won't need locking code within cache stores -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (ISPN-20) check whether locking in JDBC cache stores can be replaced with SELECT FOR UPDATE

by Manik Surtani (JIRA)

[ https://issues.jboss.org/browse/ISPN-20?page=com.atlassian.jira.plugin.sy... ] Manik Surtani updated ISPN-20: ------------------------------ Assignee: Trustin Lee (was: Mircea Markus) Fix Version/s: 5.1.0.BETA1 5.1.0.Final (was: 5.2.0.Final) > check whether locking in JDBC cache stores can be replaced with SELECT FOR UPDATE > --------------------------------------------------------------------------------- > > Key: ISPN-20 > URL: https://issues.jboss.org/browse/ISPN-20 > Project: Infinispan > Issue Type: Feature Request > Components: Loaders and Stores, Locking and Concurrency > Reporter: Mircea Markus > Assignee: Trustin Lee > Labels: hackathon > Fix For: 5.1.0.BETA1, 5.1.0.Final > > > Not sure whether the 'outside' locking (MVCC) can't be used so that we won't need locking code within cache stores -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (ISPN-61) Transaction 2-phase protocol optimizations

by Manik Surtani (JIRA)

[ https://issues.jboss.org/browse/ISPN-61?page=com.atlassian.jira.plugin.sy... ] Manik Surtani updated ISPN-61: ------------------------------ Priority: Blocker (was: Major) > Transaction 2-phase protocol optimizations > ------------------------------------------ > > Key: ISPN-61 > URL: https://issues.jboss.org/browse/ISPN-61 > Project: Infinispan > Issue Type: Feature Request > Affects Versions: 4.0.0.ALPHA4 > Reporter: Mircea Markus > Assignee: Mircea Markus > Priority: Blocker > Fix For: 5.1.0.BETA1, 5.1.0.Final > > > Following 2 optimizations might be implemented with respect to transactions. > 1) From an email on infinispan-dev (horizon-dev actually): > if there are only two members int the cluster always use an 1PC. If the 1st phase fails remotely, then also rollback locally. This would reduce one network roundtrip. > While this is an interesting thought, it does raise the potential for race conditions - since this decision will have to be taken in the TxInterceptor in the beforeCompletion phase of a transaction, and by the time the call gets to the interceptor for replication, the topology may have changed such that you need to replicate to 2 instead of 1 other peer. Which would mean a 2PC again. So it does need some thought. > 2) when asked to prepare, a participant might return a value indicating that no changes were made (read-only participant), so this one won't need an commit message, so less roundtrip. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (ISPN-462) HTTP and EJB session management for WebSphere

by Manik Surtani (JIRA)

HTTP and EJB session management for WebSphere --------------------------------------------- Key: ISPN-462 URL: https://jira.jboss.org/browse/ISPN-462 Project: Infinispan Issue Type: Feature Request Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 5.1.0.BETA1, 5.1.0.Final Session management plugin for WebSphere, to allow running WebSphere in non-clustered mode and having all clustering of session state managed by Infinispan. -- 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

12 years, 10 months

1
3
0 / 0

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

by Manik Surtani (JIRA)

[ https://issues.jboss.org/browse/ISPN-31?page=com.atlassian.jira.plugin.sy... ] Manik Surtani updated ISPN-31: ------------------------------ Fix Version/s: 5.2.0.Final (was: 5.1.0.BETA1) (was: 5.1.0.Final) Forum Reference: http://lists.jboss.org/pipermail/infinispan-dev/2009-July/000931.html (was: http://lists.jboss.org/pipermail/infinispan-dev/2009-July/000931.html) > JPA based cache store > --------------------- > > Key: ISPN-31 > URL: https://issues.jboss.org/browse/ISPN-31 > Project: Infinispan > Issue Type: Feature Request > Components: Loaders and Stores > Reporter: Manik Surtani > Assignee: Dan Berindei > Fix For: 5.2.0.Final > > > Store that uses JPA for persistence -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (ISPN-466) HTTP session management for Jetty

by Manik Surtani (JIRA)

HTTP session management for Jetty --------------------------------- Key: ISPN-466 URL: https://jira.jboss.org/browse/ISPN-466 Project: Infinispan Issue Type: Feature Request Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 5.1.0.BETA1, 5.1.0.Final Session management plugin for Tomcat, to allow running Tomcat in non-clustered mode and having all clustering of session state managed by Infinispan. -- 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

12 years, 10 months

2
5
0 / 0

[JBoss JIRA] Created: (ISPN-464) HTTP and EJB session management for Glassfish

by Manik Surtani (JIRA)

HTTP and EJB session management for Glassfish --------------------------------------------- Key: ISPN-464 URL: https://jira.jboss.org/browse/ISPN-464 Project: Infinispan Issue Type: Feature Request Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 5.1.0.BETA1, 5.1.0.Final Session management plugin for WebSphere, to allow running Oracle WebLogic in non-clustered mode and having all clustering of session state managed by Infinispan. -- 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

12 years, 10 months

1
4
0 / 0

[JBoss JIRA] Created: (ISPN-463) HTTP and EJB session management for WebLogic

by Manik Surtani (JIRA)

HTTP and EJB session management for WebLogic -------------------------------------------- Key: ISPN-463 URL: https://jira.jboss.org/browse/ISPN-463 Project: Infinispan Issue Type: Feature Request Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 5.1.0.BETA1, 5.1.0.Final Session management plugin for WebSphere, to allow running WebSphere in non-clustered mode and having all clustering of session state managed by Infinispan. -- 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

12 years, 10 months

1
5
0 / 0

[JBoss JIRA] Created: (ISPN-224) Separate Cache metrics into differen subservices in Jopr

by Galder Zamarreno (JIRA)

Separate Cache metrics into differen subservices in Jopr -------------------------------------------------------- Key: ISPN-224 URL: https://jira.jboss.org/jira/browse/ISPN-224 Project: Infinispan Issue Type: Feature Request Components: JMX, reporting and management Reporter: Galder Zamarreno Assignee: Galder Zamarreno Fix For: 4.1.0.BETA1 The current Jopr plugin shows a Cache with different metrics for each individual metric available in the cache, i.e. cache stores, cache loades, average repl time...etc. This set up was fine when there was only a handful of metrics, but we after adding all the different managed attributes, we have around ~43 metrics now (some obviously but not always be present, i.e. metrics related to cache stores, deadlock detecting manager...etc), but they still appear but with no metrics at all. So, as the number of metrics increase, you have a massive list of different values under Cache. I think it'd be good to separate attributes from different interceptors into different services under Cache, i.e Statistics, Cache Store, Passivation/Activation...etc. This would make it cleaner to read to the user. -- 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

12 years, 10 months

2
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues June 2011