July 2013 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-506) Infinispan should have a notion of comparable dataversion for handling external db updates

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/ISPN-506?page=com.atlassian.jira.plugin.s... ] Max Rydahl Andersen commented on ISPN-506: ------------------------------------------ Will we ever get this ? :) > Infinispan should have a notion of comparable dataversion for handling external db updates > ------------------------------------------------------------------------------------------ > > Key: ISPN-506 > URL: https://issues.jboss.org/browse/ISPN-506 > Project: Infinispan > Issue Type: Feature Request > Reporter: Max Rydahl Andersen > Assignee: Galder Zamarreño > > As discussed in hotel bar -- 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-376) Enable Infinispan standalone's Channel to be plugged with MessageListeners

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-376?page=com.atlassian.jira.plugin.s... ] Mircea Markus updated ISPN-376: ------------------------------- Fix Version/s: (was: 6.0.0.Final) > Enable Infinispan standalone's Channel to be plugged with MessageListeners > -------------------------------------------------------------------------- > > Key: ISPN-376 > URL: https://issues.jboss.org/browse/ISPN-376 > Project: Infinispan > Issue Type: Feature Request > Components: RPC > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > > Investigate what would need doing to enable Infinispan to receive a JGroups' Channel or ChannelFactory that allows users to add their own message listeners when such clients want to be sending rpcs around. > Brian will be using a solution like this for the AS case but since AS is owner of the Channel, this is relatively easy for it assuming that JGroups has the right API for it. -- 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-376) Enable Infinispan standalone's Channel to be plugged with MessageListeners

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-376?page=com.atlassian.jira.plugin.s... ] Mircea Markus resolved ISPN-376. -------------------------------- Resolution: Out of Date seems out of date, please reopen if still required. > Enable Infinispan standalone's Channel to be plugged with MessageListeners > -------------------------------------------------------------------------- > > Key: ISPN-376 > URL: https://issues.jboss.org/browse/ISPN-376 > Project: Infinispan > Issue Type: Feature Request > Components: RPC > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > > Investigate what would need doing to enable Infinispan to receive a JGroups' Channel or ChannelFactory that allows users to add their own message listeners when such clients want to be sending rpcs around. > Brian will be using a solution like this for the AS case but since AS is owner of the Channel, this is relatively easy for it assuming that JGroups has the right API for it. -- 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-706) Enable Hot Rod server caches to be accessed without extra marshalling

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-706?page=com.atlassian.jira.plugin.s... ] Mircea Markus resolved ISPN-706. -------------------------------- Resolution: Duplicate Issue Was implemented as part of ISPN-2281. > Enable Hot Rod server caches to be accessed without extra marshalling > --------------------------------------------------------------------- > > Key: ISPN-706 > URL: https://issues.jboss.org/browse/ISPN-706 > Project: Infinispan > Issue Type: Feature Request > Components: Remote protocols > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > > People are starting to ask for this: > Write to Hot Rod remotely and then being able to retrieve objects from the server side cache without any extra steps. At the moment, a marshalling layer is necessary so that those byte[] are converted into objects. -- 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-706) Enable Hot Rod server caches to be accessed without extra marshalling

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-706?page=com.atlassian.jira.plugin.s... ] Mircea Markus updated ISPN-706: ------------------------------- Fix Version/s: (was: 6.0.0.Final) > Enable Hot Rod server caches to be accessed without extra marshalling > --------------------------------------------------------------------- > > Key: ISPN-706 > URL: https://issues.jboss.org/browse/ISPN-706 > Project: Infinispan > Issue Type: Feature Request > Components: Remote protocols > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > > People are starting to ask for this: > Write to Hot Rod remotely and then being able to retrieve objects from the server side cache without any extra steps. At the moment, a marshalling layer is necessary so that those byte[] are converted into objects. -- 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-61) Dynamically switch between single and two phase commit based on cluster size

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-61?page=com.atlassian.jira.plugin.sy... ] Mircea Markus updated ISPN-61: ------------------------------ Fix Version/s: (was: 6.0.0.Final) > Dynamically switch between single and two phase commit based on cluster size > ---------------------------------------------------------------------------- > > 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 > > 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, 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-375) Enable Hot Rod clients to start transactions

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-375?page=com.atlassian.jira.plugin.s... ] Mircea Markus updated ISPN-375: ------------------------------- Fix Version/s: (was: 6.0.0.Alpha3) > Enable Hot Rod clients to start transactions > -------------------------------------------- > > Key: ISPN-375 > URL: https://issues.jboss.org/browse/ISPN-375 > Project: Infinispan > Issue Type: Feature Request > Components: Remote protocols > Reporter: Galder Zamarreño > Assignee: Michael Musgrove > Priority: Blocker > Labels: hackathon > > It might be useful to allow Hot Rod clients to start transactions within Hot Rod servers. The possibility of clients participating in the actual transaction, i.e. being an XAResource, should not be imposed since this might be less than trivial to achieve in non-Java environments. The alternative would be to allow clients to start Hot Rod server local transactions only. > This would require enhancing Hot Rod spec to have some begin/commit/rollback commands that return a tx id, and for clients to be able to send this id as part of each command that should participate in the transaction. > Pitfalls to avoid include avoiding a transaction to be propagated over several Hot Rod servers. IOW, to simplify things, if a tx is started in server A, all ops within that tx should be directed to tx. Load balancing could still happen but would need to be tx sticky. -- 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-1186) Document different approaches for working with cache statistics for local cache and remote cache (HotRod)

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-1186?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-1186: -------------------------------- Fix Version/s: (was: 6.0.0.Final) > Document different approaches for working with cache statistics for local cache and remote cache (HotRod) > ---------------------------------------------------------------------------------------------------------- > > Key: ISPN-1186 > URL: https://issues.jboss.org/browse/ISPN-1186 > Project: Infinispan > Issue Type: Task > Affects Versions: 4.2.1.FINAL > Reporter: Martin Gencur > Assignee: Mircea Markus > Priority: Optional > > The documentation for Infinispan should mention different approaches for accessing remote cache (HotRod) and local (default) cache statistics. For example, there is not "evictions" statistics for remote cache. Maybe it would be enough to just mention different classes that hold these statistics (Stats and RemoteStatistics) and the way of getting them. > It should be mentioned most likely somewhere under http://community.jboss.org/wiki/infinispan -- 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-2317) Distributed Callable with automatic filled keys in environment where current node = owner

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2317?page=com.atlassian.jira.plugin.... ] Mircea Markus commented on ISPN-2317: ------------------------------------- [~tfromm] so each key is being processed numOwners time? > Distributed Callable with automatic filled keys in environment where current node = owner > ----------------------------------------------------------------------------------------- > > Key: ISPN-2317 > URL: https://issues.jboss.org/browse/ISPN-2317 > Project: Infinispan > Issue Type: Feature Request > Components: Distributed Execution and Map/Reduce > Affects Versions: 5.1.7.Final > Reporter: Thomas Fromm > Assignee: Vladimir Blagojevic > > In a distributed cache I need to process every key one time. My solution is ATM to create a distributed call and on every node walk through the keyset of the cache and process every node, where the current node is the owner. > This solution works, but is not really nice. > I'd like to have a specific Distributed callable for this or an flag/option to enable that the keys where the current node is owner are used at setEnvironment(...). -- 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-2317) Distributed Callable with automatic filled keys in environment where current node = owner

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2317?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2317: -------------------------------- Fix Version/s: (was: 6.0.0.Final) > Distributed Callable with automatic filled keys in environment where current node = owner > ----------------------------------------------------------------------------------------- > > Key: ISPN-2317 > URL: https://issues.jboss.org/browse/ISPN-2317 > Project: Infinispan > Issue Type: Feature Request > Components: Distributed Execution and Map/Reduce > Affects Versions: 5.1.7.Final > Reporter: Thomas Fromm > Assignee: Vladimir Blagojevic > > In a distributed cache I need to process every key one time. My solution is ATM to create a distributed call and on every node walk through the keyset of the cache and process every node, where the current node is the owner. > This solution works, but is not really nice. > I'd like to have a specific Distributed callable for this or an flag/option to enable that the keys where the current node is owner are used at setEnvironment(...). -- 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