February 2014 - infinispan-issues

[JBoss JIRA] (ISPN-3355) Add support for clustered listeners

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-3355?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-3355: -------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/2389 > Add support for clustered listeners > ----------------------------------- > > Key: ISPN-3355 > URL: https://issues.jboss.org/browse/ISPN-3355 > Project: Infinispan > Issue Type: Feature Request > Components: Core > Reporter: Mircea Markus > Assignee: William Burns > Fix For: 7.0.0.Final > > > As opposed to the current listener approach in Infinispan ( a listener instance is invoked on the data owners ), this JIRA is about adding support for a cluster listener: the same listener instance that is notified disregarding of data ownership ( RPC calls involved). > Due to the fact that the listener notification might involve an RPC, it is nice to be able to specify filters on these listeners. > The clustered listener support opens the way for some interesting architectures: > * persistent/continuous queries: the query is transformed in a filter. On each notification, the listener (stateful) updates the query state > * simplistic CEP can be built on top of the persistent query described above > * remote/hotrod notifications might be based on clustered listeners as well. -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4055) Upgrade to JGroups 3.5.0.Alpha1

by Pedro Ruivo (JIRA)

Pedro Ruivo created ISPN-4055: --------------------------------- Summary: Upgrade to JGroups 3.5.0.Alpha1 Key: ISPN-4055 URL: https://issues.jboss.org/browse/ISPN-4055 Project: Infinispan Issue Type: Component Upgrade Reporter: Pedro Ruivo Assignee: Pedro Ruivo Fix For: 7.0.0.Alpha1, 7.0.0.Final -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4055) Upgrade to JGroups 3.5.0.Alpha1

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-4055?page=com.atlassian.jira.plugin.... ] Work on ISPN-4055 started by Pedro Ruivo. > Upgrade to JGroups 3.5.0.Alpha1 > ------------------------------- > > Key: ISPN-4055 > URL: https://issues.jboss.org/browse/ISPN-4055 > Project: Infinispan > Issue Type: Component Upgrade > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Fix For: 7.0.0.Alpha1, 7.0.0.Final > > -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4018) Write skew should not be check if conditional operations does not change the value

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-4018?page=com.atlassian.jira.plugin.... ] Dan Berindei commented on ISPN-4018: ------------------------------------ Ok, I did some more reading and I guess you're right, not even snapshot isolation requires a write skew check on all the read keys. And since a conditional command only modifies the key if the condition is met, a failed {{putIfAbsent(x, w)}} should not count as a write on {{x}}. > Write skew should not be check if conditional operations does not change the value > ---------------------------------------------------------------------------------- > > Key: ISPN-4018 > URL: https://issues.jboss.org/browse/ISPN-4018 > Project: Infinispan > Issue Type: Bug > Components: Core, Transactions > Affects Versions: 6.0.1.Final > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Fix For: 7.0.0.Alpha1, 7.0.0.Final > > > Currently, if a conditional operation does no perform the update, we still perform the check. however, the write never happened. It simple makes no sense. > However, if a write succeeds after, the write skew check must be performed for the key. -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4002) Allow the reduce phase to store elements into result cache

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-4002?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-4002: -------------------------------------- Summary: Allow the reduce phase to store elements into result cache (was: Allow the reduce phase to store elements into an intermediate cache ) > Allow the reduce phase to store elements into result cache > ----------------------------------------------------------- > > Key: ISPN-4002 > URL: https://issues.jboss.org/browse/ISPN-4002 > Project: Infinispan > Issue Type: Feature Request > Components: Core, Distributed Execution and Map/Reduce > Reporter: Mircea Markus > Assignee: Vladimir Blagojevic > > In the situation in which the result of the Map/Reduce task is large, returning it to the originator does not work, as the originator would run OOM. In order to drop this limitation, would be good to: > - have a result cache > - put all the M/R entries into this result cache > It should be possible to specify this cache to the Map/Reduce task to be executed (cache name), as users might reuse the cache and configure it externally. > > The caller will be notified once the data Map/Reduce is finished. We'd need a way for the user to get all the keys in this cache for further processing. -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4002) Allow the reduce phase to store elements into an intermediate cache

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-4002?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic commented on ISPN-4002: ------------------------------------------- Yes, [~dan.berindei] intermediate confuses users with our temp/intermediate caches used between map/reduce phases. I'll update it > Allow the reduce phase to store elements into an intermediate cache > -------------------------------------------------------------------- > > Key: ISPN-4002 > URL: https://issues.jboss.org/browse/ISPN-4002 > Project: Infinispan > Issue Type: Feature Request > Components: Core, Distributed Execution and Map/Reduce > Reporter: Mircea Markus > Assignee: Vladimir Blagojevic > > In the situation in which the result of the Map/Reduce task is large, returning it to the originator does not work, as the originator would run OOM. In order to drop this limitation, would be good to: > - have a result cache > - put all the M/R entries into this result cache > It should be possible to specify this cache to the Map/Reduce task to be executed (cache name), as users might reuse the cache and configure it externally. > > The caller will be notified once the data Map/Reduce is finished. We'd need a way for the user to get all the keys in this cache for further processing. -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4035) SingleFileStore.FileEntry.compareTo is wrong

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-4035?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-4035: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/2400 > SingleFileStore.FileEntry.compareTo is wrong > -------------------------------------------- > > Key: ISPN-4035 > URL: https://issues.jboss.org/browse/ISPN-4035 > Project: Infinispan > Issue Type: Bug > Components: Core, Loaders and Stores > Affects Versions: 6.0.1.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Critical > Fix For: 7.0.0.Alpha1 > > > Because {{FileEntry.compareTo(fe)}} never returns 0, allocated entries are not properly removed from the free list (at least on IBM JDK 6). -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4021) Allow each Map/Reduce task to use a different cache configuration

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-4021?page=com.atlassian.jira.plugin.... ] Mircea Markus commented on ISPN-4021: ------------------------------------- indeed I think option b) should be enough and it's quite simple/flexible. > Allow each Map/Reduce task to use a different cache configuration > ----------------------------------------------------------------- > > Key: ISPN-4021 > URL: https://issues.jboss.org/browse/ISPN-4021 > Project: Infinispan > Issue Type: Feature Request > Components: Core, Distributed Execution and Map/Reduce > Affects Versions: 6.0.1.Final > Reporter: Dan Berindei > Assignee: Vladimir Blagojevic > Fix For: 7.0.0.Final > > > Some Map/Reduce tasks may need a cache store and eviction, some may not. Each task should be able to use its own cache configuration. -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4036) StateConsumerImpl.isKeyUpdated searches for the key in the values collection

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-4036?page=com.atlassian.jira.plugin.... ] Dan Berindei commented on ISPN-4036: ------------------------------------ [~pruivo] I missed your comment and I already created a PR, since I already had the fix in a local branch. > StateConsumerImpl.isKeyUpdated searches for the key in the values collection > ---------------------------------------------------------------------------- > > Key: ISPN-4036 > URL: https://issues.jboss.org/browse/ISPN-4036 > Project: Infinispan > Issue Type: Bug > Components: Core, State Transfer > Affects Versions: 6.0.1.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Critical > Fix For: 7.0.0.Alpha1 > > > Introduced by the ISPN-3443 fix. I changed the {{updatedKeys}} HashSet to be an EquivalendConcurrentHashMap, but I forgot to change the {{contains(key)}} call to {{containsKey(key)}}. Since we use the same value for all the keys, it means state transfer might skip more keys than it should have. -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4054) Scripts to analyze test failures and corresponding issues

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-4054?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-4054: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/2399 > Scripts to analyze test failures and corresponding issues > --------------------------------------------------------- > > Key: ISPN-4054 > URL: https://issues.jboss.org/browse/ISPN-4054 > Project: Infinispan > Issue Type: Task > Components: Test Suite - Core > Affects Versions: 6.0.1.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 7.0.0.Alpha1 > > > Need an easy way to find scripts that fail in CI but don't have a corresponding issue in JIRA, or are not in the unstable group. -- 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

10 years, 11 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues February 2014