March 2010 - infinispan-issues - Jboss List Archives

[JBoss JIRA] Commented: (ISPN-29) Cache server and client module

by Manik Surtani (JIRA)

[ https://jira.jboss.org/jira/browse/ISPN-29?page=com.atlassian.jira.plugin... ] Manik Surtani commented on ISPN-29: ----------------------------------- Question to address: what happens when a connection breaks between client and server? What sort of keepalives, etc do we have, e.g., a ping-pong protocol? > Cache server and client module > ------------------------------ > > Key: ISPN-29 > URL: https://jira.jboss.org/jira/browse/ISPN-29 > Project: Infinispan > Issue Type: Feature Request > Components: Cache Server > Reporter: Manik Surtani > Assignee: Galder Zamarreno > Priority: Blocker > Fix For: 4.1.0.BETA1, 4.1.0.Final > > > To be built on top of the cache. > Transports should be pluggable - Initially XNIO, future community contribs using Apache MINA, Netty, JDK7 NIO2, native, etc. > Protocols should be pluggable - memcached text-based, custom binary with server topology information > Test with various memcached clients (java and non-java) > More details on this wiki page: > http://www.jboss.org/community/wiki/Clientandservermodules -- 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

14 years, 12 months

1
0
0 / 0

[JBoss JIRA] Commented: (ISPN-29) Cache server and client module

by Manik Surtani (JIRA)

[ https://jira.jboss.org/jira/browse/ISPN-29?page=com.atlassian.jira.plugin... ] Manik Surtani commented on ISPN-29: ----------------------------------- Transactions: as per this discussion (http://lists.jboss.org/pipermail/infinispan-dev/2010-March/002497.html) we won't be implementing transactions now, but would consider for later. > Cache server and client module > ------------------------------ > > Key: ISPN-29 > URL: https://jira.jboss.org/jira/browse/ISPN-29 > Project: Infinispan > Issue Type: Feature Request > Components: Cache Server > Reporter: Manik Surtani > Assignee: Galder Zamarreno > Priority: Blocker > Fix For: 4.1.0.BETA1, 4.1.0.Final > > > To be built on top of the cache. > Transports should be pluggable - Initially XNIO, future community contribs using Apache MINA, Netty, JDK7 NIO2, native, etc. > Protocols should be pluggable - memcached text-based, custom binary with server topology information > Test with various memcached clients (java and non-java) > More details on this wiki page: > http://www.jboss.org/community/wiki/Clientandservermodules -- 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

14 years, 12 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/jira/browse/ISPN-180?page=com.atlassian.jira.plugi... ] Manik Surtani commented on ISPN-180: ------------------------------------ Additional configuration parameters - hints - could be optionally provided for each instance. These hints - MachineId, RackId, SiteId - could be used (if provided) in the hash function that places nodes on the hash wheel such that state is not "backed up" on the same machine, rack, etc. > Colocated nodes should be handled in DIST > ----------------------------------------- > > Key: ISPN-180 > URL: https://jira.jboss.org/jira/browse/ISPN-180 > Project: Infinispan > Issue Type: Feature Request > Reporter: Manik Surtani > Assignee: Manik Surtani > Fix For: 4.1.0.BETA1, 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/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 12 months

1
0
0 / 0

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

by Manik Surtani (JIRA)

[ https://jira.jboss.org/jira/browse/ISPN-61?page=com.atlassian.jira.plugin... ] Manik Surtani updated ISPN-61: ------------------------------ Fix Version/s: 5.1.0.BETA1 5.1.0.Final (was: 5.0.0.BETA1) (was: 5.0.0.Final) > Transaction 2-phase protocol optimizations > ------------------------------------------ > > Key: ISPN-61 > URL: https://jira.jboss.org/jira/browse/ISPN-61 > Project: Infinispan > Issue Type: Feature Request > Affects Versions: 4.0.0.ALPHA4 > Reporter: Mircea Markus > Assignee: Mircea Markus > 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. - 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

14 years, 12 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://jira.jboss.org/jira/browse/ISPN-20?page=com.atlassian.jira.plugin... ] Manik Surtani updated ISPN-20: ------------------------------ Fix Version/s: 5.1.0.BETA1 5.1.0.Final (was: 5.0.0.BETA1) (was: 5.0.0.Final) > check whether locking in JDBC cache stores can be replaced with SELECT FOR UPDATE > --------------------------------------------------------------------------------- > > Key: ISPN-20 > URL: https://jira.jboss.org/jira/browse/ISPN-20 > Project: Infinispan > Issue Type: Feature Request > Components: Loaders and Stores, Locking and Concurrency > Reporter: Mircea Markus > Assignee: Mircea Markus > 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. - 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

14 years, 12 months

1
0
0 / 0

[JBoss JIRA] Updated: (ISPN-39) Distributed executors

by Manik Surtani (JIRA)

[ https://jira.jboss.org/jira/browse/ISPN-39?page=com.atlassian.jira.plugin... ] Manik Surtani updated ISPN-39: ------------------------------ Fix Version/s: 5.0.0.BETA1 5.0.0.Final (was: 5.1.0.BETA1) (was: 5.1.0.Final) > Distributed executors > --------------------- > > Key: ISPN-39 > URL: https://jira.jboss.org/jira/browse/ISPN-39 > Project: Infinispan > Issue Type: Feature Request > Components: RPC > Reporter: Manik Surtani > Assignee: Manik Surtani > Fix For: 5.0.0.BETA1, 5.0.0.Final > > > A new API to allow users to provide a Runnable/Callable and a set of keys to run this on, and the ability to move the code to where the data is and execute it there, returning results (if any) across a network. -- 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

14 years, 12 months

1
0
0 / 0

[JBoss JIRA] Updated: (ISPN-58) Create a TaskQueueExecutorFactory and TaskQueueScheduledExecutorFactory

by Manik Surtani (JIRA)

[ https://jira.jboss.org/jira/browse/ISPN-58?page=com.atlassian.jira.plugin... ] Manik Surtani updated ISPN-58: ------------------------------ Fix Version/s: 5.1.0.BETA1 5.1.0.Final (was: 5.0.0.BETA1) (was: 5.0.0.Final) > Create a TaskQueueExecutorFactory and TaskQueueScheduledExecutorFactory > ----------------------------------------------------------------------- > > Key: ISPN-58 > URL: https://jira.jboss.org/jira/browse/ISPN-58 > Project: Infinispan > Issue Type: Sub-task > Reporter: Manik Surtani > Assignee: Manik Surtani > Fix For: 5.1.0.BETA1, 5.1.0.Final > > > These executors will not spawn separate threads, but hook in to Google's TaskQueue API > http://code.google.com/appengine/docs/java/taskqueue/overview.html > This will enable Infinispan to run without spawning any additional threads, thereby enabling it to run on Google's App Engine runtime. > Will need to expose a URI (/taskqueueexecutor ?) which is invoked to process arbitrary Callable/Runnables. May need to use the DataStore to store the actual Callable/Runnable, and pass the taskqueueexecutor the key of the stored object. -- 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

14 years, 12 months

1
0
0 / 0

[JBoss JIRA] Created: (ISPN-262) Geographically distributed data grid

by Manik Surtani (JIRA)

Geographically distributed data grid ------------------------------------ Key: ISPN-262 URL: https://jira.jboss.org/jira/browse/ISPN-262 Project: Infinispan Issue Type: Feature Request Components: Distributed Cache, RPC, State transfer Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 5.0.0.BETA1, 5.0.0.GA WAN replication, either Live-Live or Live-Standby. Some interesting thoughts can be gleaned from JBCACHE-816 -- 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

14 years, 12 months

2
2
0 / 0

[JBoss JIRA] Resolved: (ISPN-71) Management interface

by Manik Surtani (JIRA)

[ https://jira.jboss.org/jira/browse/ISPN-71?page=com.atlassian.jira.plugin... ] Manik Surtani resolved ISPN-71. ------------------------------- Fix Version/s: 4.0.0.Final (was: 5.0.0.Final) (was: 5.0.0.BETA1) Resolution: Done > Management interface > -------------------- > > Key: ISPN-71 > URL: https://jira.jboss.org/jira/browse/ISPN-71 > Project: Infinispan > Issue Type: Feature Request > Components: JMX, reporting and management > Reporter: Manik Surtani > Assignee: Manik Surtani > Fix For: 4.0.0.Final > > > This will be built atop what we already expose in JMX. GUI console and command-line hooks need to be designed. -- 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

14 years, 12 months

1
0
0 / 0

[JBoss JIRA] Updated: (ISPN-57) Support Google App Engine

by Manik Surtani (JIRA)

[ https://jira.jboss.org/jira/browse/ISPN-57?page=com.atlassian.jira.plugin... ] Manik Surtani updated ISPN-57: ------------------------------ Fix Version/s: 5.1.0.BETA1 5.1.0.Final (was: 5.0.0.BETA1) (was: 5.0.0.Final) > Support Google App Engine > ------------------------- > > Key: ISPN-57 > URL: https://jira.jboss.org/jira/browse/ISPN-57 > Project: Infinispan > Issue Type: Feature Request > Components: Core API > Reporter: Adrian Cole > Assignee: Manik Surtani > Fix For: 5.1.0.BETA1, 5.1.0.Final > > > Google App Engine for Java is a restricted JVM. It prevents such things as file access and thread creation. Currently, Infinispan requires at least thread creation and depending on the cachestore mechanism, potentially file as well. > This is a container to investigate other related issues that may prevent Infinispan from running on GAE. -- 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

14 years, 12 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues March 2010