July 2013 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-3) Should use JGroups scoping

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/ISPN-3?page=com.atlassian.jira.plugin.sys... ] Bela Ban commented on ISPN-3: ----------------------------- Yes, this still makes sense, but I don't think SCOPE should be used. Instead, here we should use the Infinispan internal thread pool which uses JGroups' Async Invocation API. If member P sends out modifications P5 and P6 for different web sessions (e.g.), then JGroups would deliver P5 and P6 sequentialy, because they're sent by the same member. Here, Infinispan could decide to deliver P5 and P6 in parallel, based on some information attached to the RPC. > Should use JGroups scoping > -------------------------- > > Key: ISPN-3 > URL: https://issues.jboss.org/browse/ISPN-3 > Project: Infinispan > Issue Type: Feature Request > Components: RPC > Reporter: Manik Surtani > Assignee: Vladimir Blagojevic > > JGroups will provide a scoping API. This allows better concurrency in the JGroups channel. By default, the scope used should be the cache name, although use of other scopes should be allowed such as GlobalTransaction. Also need to consider allowing arbitrary scopes, passed in by user code. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

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

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-57?page=com.atlassian.jira.plugin.sy... ] Mircea Markus updated ISPN-57: ------------------------------ Fix Version/s: (was: 6.0.0.Final) > Support Google App Engine > ------------------------- > > Key: ISPN-57 > URL: https://issues.jboss.org/browse/ISPN-57 > Project: Infinispan > Issue Type: Feature Request > Components: Core API > Reporter: Adrian Cole > Assignee: Manik Surtani > > 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, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-449) Streaming over Hot Rod

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-449?page=com.atlassian.jira.plugin.s... ] Mircea Markus updated ISPN-449: ------------------------------- Fix Version/s: (was: 6.0.0.Final) > Streaming over Hot Rod > ---------------------- > > Key: ISPN-449 > URL: https://issues.jboss.org/browse/ISPN-449 > Project: Infinispan > Issue Type: Feature Request > Components: Remote protocols > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Labels: hackathon > > Extend large object support/streaming to Hot Rod -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-924) Support Atomic arithmetic operations in the API

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-924?page=com.atlassian.jira.plugin.s... ] Mircea Markus updated ISPN-924: ------------------------------- Fix Version/s: (was: 6.0.0.Final) > Support Atomic arithmetic operations in the API > ----------------------------------------------- > > Key: ISPN-924 > URL: https://issues.jboss.org/browse/ISPN-924 > Project: Infinispan > Issue Type: Feature Request > Components: Core API > Reporter: Erik Salter > Assignee: Manik Surtani > > It would be useful if Infinispan supported cluster-wide atomic operations for java.lang.Number types in the API -- similar to the AtomicX API in Java. > Right now, to cobble this functionality, we'd need to do something like: > - Start a tx > - Single-lock a key > - Get and increment > - Commit > - And, of course, handle the cache exceptions =) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1103) Soft schema-based storage

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-1103?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-1103: -------------------------------- Fix Version/s: (was: 6.0.0.Final) > Soft schema-based storage > ------------------------- > > Key: ISPN-1103 > URL: https://issues.jboss.org/browse/ISPN-1103 > Project: Infinispan > Issue Type: Feature Request > Components: Core API > Reporter: Manik Surtani > Assignee: Randall Hauch > Priority: Critical > > This JIRA is about storing metadata alongside values. Perhaps encapsulating values as SchematicValues, which could be described as: > {code} > class SchematicValue { > String jsonMetadata; > String jsonObject; > } > {code} > Metadata would allow for a few interesting features: > * Extracting of lifespan and timestamp data if manipulated over a remote protocol (REST, HotRod, etc) > * Content type for REST responses > * Timestamps and SHA-1 hashes, useful for for HTTP headers (e.g., ETag, Cache-control, etc.) > * Validation information (may not be processed by Infinispan, but can be used by client libs) > * Classloader/marshaller/classdef version info > * General structure of the information stored > * Reference to the schema for this document > * Storage of older versions -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2501) State transfer optimizations

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2501?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2501: -------------------------------- Fix Version/s: (was: 6.0.0.Alpha1) > State transfer optimizations > ---------------------------- > > Key: ISPN-2501 > URL: https://issues.jboss.org/browse/ISPN-2501 > Project: Infinispan > Issue Type: Enhancement > Components: State transfer > Affects Versions: 5.2.0.Beta3 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > > There are two obvious optimizations possible in the code that handles installation of a new topology. > 1. Currently a new topology is not confirmed until the node successfully sends START_STATE_TRANSFER requests to all nodes it wants to fetch segments from. This does not wait for the actual data to arrive but it still blocks quite a lot. To fix this we need to confirm the topology right after transactions were received. > 2. Fetching transactions from other members is done serially. To improve it we could split it into multiple concurrent tasks. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1599) Split entry locking in Data Lock(s) and Structure Lock(s)

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-1599?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-1599: -------------------------------- Fix Version/s: (was: 6.0.0.Final) > Split entry locking in Data Lock(s) and Structure Lock(s) > --------------------------------------------------------- > > Key: ISPN-1599 > URL: https://issues.jboss.org/browse/ISPN-1599 > Project: Infinispan > Issue Type: Enhancement > Reporter: Sanne Grinovero > Assignee: Manik Surtani > > See mailing list thread: > http://lists.jboss.org/pipermail/infinispan-dev/2011-December/009605.html > http://infinispan.markmail.org/thread/k7sucf5dnuenuuf7 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1543) Split CacheImpl into TransactionalCache and NonTransactionalCache

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-1543?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-1543: -------------------------------- Fix Version/s: (was: 6.0.0.Final) > Split CacheImpl into TransactionalCache and NonTransactionalCache > ------------------------------------------------------------------ > > Key: ISPN-1543 > URL: https://issues.jboss.org/browse/ISPN-1543 > Project: Infinispan > Issue Type: Feature Request > Components: Core API > Affects Versions: 5.1.0.BETA4 > Reporter: Mircea Markus > Assignee: Mircea Markus > Priority: Minor > Labels: refactor > > There is a lot of unnecessary complexity in CacheImpl caused by handling two types of caches: transactional and non-transactional. > This code (and potentially InvocationContextContainer) can be simplified a lot by splitting the logic into two cache implementations: TransactionalCache and NonTransactionalCache. The common logic would be moved in an AbstractCache. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3231) Skip TransactionCompletionNotification for autoCommit transactions with 1PC commit

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3231?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3231: -------------------------------- Fix Version/s: 6.0.0.Final > Skip TransactionCompletionNotification for autoCommit transactions with 1PC commit > ---------------------------------------------------------------------------------- > > Key: ISPN-3231 > URL: https://issues.jboss.org/browse/ISPN-3231 > Project: Infinispan > Issue Type: Enhancement > Affects Versions: 5.2.6.Final > Reporter: Mircea Markus > Assignee: Mircea Markus > Fix For: 6.0.0.Alpha1, 6.0.0.Final > > > autoCommit transactions with 1PC commit is unreliable for concurrent access, so locking + tx completion notification can be skipped. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3) Should use JGroups scoping

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3?page=com.atlassian.jira.plugin.sys... ] Mircea Markus commented on ISPN-3: ---------------------------------- [~belaban] does this still make sense? > Should use JGroups scoping > -------------------------- > > Key: ISPN-3 > URL: https://issues.jboss.org/browse/ISPN-3 > Project: Infinispan > Issue Type: Feature Request > Components: RPC > Reporter: Manik Surtani > Assignee: Vladimir Blagojevic > Fix For: 6.0.0.Final > > > JGroups will provide a scoping API. This allows better concurrency in the JGroups channel. By default, the scope used should be the cache name, although use of other scopes should be allowed such as GlobalTransaction. Also need to consider allowing arbitrary scopes, passed in by user code. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues July 2013