November 2014 - infinispan-issues

[JBoss JIRA] (ISPN-4827) Add JMX attributes to inspect partition health

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4827?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-4827: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1160718 > Add JMX attributes to inspect partition health > ---------------------------------------------- > > Key: ISPN-4827 > URL: https://issues.jboss.org/browse/ISPN-4827 > Project: Infinispan > Issue Type: Sub-task > Components: JMX, reporting and management > Affects Versions: 7.0.0.CR1 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 7.0.0.CR2, 7.0.0.Final > > -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5000) Cleanup rebalance confirmation collector when node is not coord

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5000?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-5000: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1166243 > Cleanup rebalance confirmation collector when node is not coord > --------------------------------------------------------------- > > Key: ISPN-5000 > URL: https://issues.jboss.org/browse/ISPN-5000 > Project: Infinispan > Issue Type: Bug > Components: State Transfer > Affects Versions: 7.0.1.Final > Reporter: Radim Vansa > Priority: Critical > > The rebalance confirmation collector is not properly cleared when node becomes non-coordinator. Therefore, when it becomes coordinator, it does not start the rebalance. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5000) Cleanup rebalance confirmation collector when node is not coord

by Radim Vansa (JIRA)

Radim Vansa created ISPN-5000: --------------------------------- Summary: Cleanup rebalance confirmation collector when node is not coord Key: ISPN-5000 URL: https://issues.jboss.org/browse/ISPN-5000 Project: Infinispan Issue Type: Bug Components: State Transfer Affects Versions: 7.0.1.Final Reporter: Radim Vansa Priority: Critical The rebalance confirmation collector is not properly cleared when node becomes non-coordinator. Therefore, when it becomes coordinator, it does not start the rebalance. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3402) Add JDBC Cache Store config to RHQ plugin

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-3402?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-3402: ----------------------------------------------- Tomas Sykora <tsykora(a)redhat.com> changed the Status of [bug 1144491|https://bugzilla.redhat.com/show_bug.cgi?id=1144491] from ON_QA to ASSIGNED > Add JDBC Cache Store config to RHQ plugin > ----------------------------------------- > > Key: ISPN-3402 > URL: https://issues.jboss.org/browse/ISPN-3402 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores, Server > Reporter: William Burns > Assignee: William Burns > Fix For: 7.0.0.CR1, 7.0.0.Final > > > ISPN-3350 was added to enhance some of the RHQ endpoints to allow for better runtime configuration support. However ISPN-3290 is also concurrently changing cache stores. Some changes for ISPN-3290 were mentioned to be possibly changing how the JDBC cache stores are configured and as such this has been excluded from ISPN-3350 to not implement it twice. > This is just to add in the support JDBC cache stores as they are missing. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4757) Provide option to receive remote event filter/converter callbacks with raw data

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-4757?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-4757: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/3084 > Provide option to receive remote event filter/converter callbacks with raw data > ------------------------------------------------------------------------------- > > Key: ISPN-4757 > URL: https://issues.jboss.org/browse/ISPN-4757 > Project: Infinispan > Issue Type: Enhancement > Components: Remote Protocols > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 7.1.0.Final > > > As agreed in the forum post link, providing raw data can avoid serialization costs and can avoid classloading problems. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4999) Introduce a Listener interface

by Jim Crossley (JIRA)

Jim Crossley created ISPN-4999: ---------------------------------- Summary: Introduce a Listener interface Key: ISPN-4999 URL: https://issues.jboss.org/browse/ISPN-4999 Project: Infinispan Issue Type: Feature Request Reporter: Jim Crossley The notifications API is strictly annotations-based, which is awkward for more dynamic, non-Java JVM languages. I think a Listener interface with a single method taking an Event parameter would be a far simpler approach. It wouldn't have to replace the current API, merely complement it. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-694) Create expiration notification for in-memory cache entries

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-694?page=com.atlassian.jira.plugin.s... ] Galder Zamarreño updated ISPN-694: ---------------------------------- Assignee: (was: Galder Zamarreño) > Create expiration notification for in-memory cache entries > ---------------------------------------------------------- > > Key: ISPN-694 > URL: https://issues.jboss.org/browse/ISPN-694 > Project: Infinispan > Issue Type: Feature Request > Components: Eviction > Environment: any > Reporter: Edouard Boily > Attachments: 01.patch > > > Create a CacheEntryExpired notification and make EvictionManager send this notification when a cache entry is evicted because it is expired. > Also mage sure the cache entry value is sent over in the event. > CacheEntryEvicted notification should also send the entry value in the event. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4444) After state transfer, a node is able to read keys it no longer owns from its data container

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-4444?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-4444: ------------------------------ Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/3083 > After state transfer, a node is able to read keys it no longer owns from its data container > ------------------------------------------------------------------------------------------- > > Key: ISPN-4444 > URL: https://issues.jboss.org/browse/ISPN-4444 > Project: Infinispan > Issue Type: Bug > Components: Core, State Transfer > Affects Versions: 7.0.0.Alpha4 > Reporter: Dan Berindei > Assignee: Pedro Ruivo > Priority: Critical > Fix For: 7.1.0.Alpha1 > > > When state transfer ends and each node receives a CH_UPDATE command from the coordinator, it first installs the new topology and then it starts invalidating entries it no longer owns. > However, there are two cases when the node can still read its stale values: > 1. If L1 is enabled, it will look in the local DataContainer first, regardless of the key's location. > 2. If L1 is disabled, but the key was removed on the new owners, the node will still look up the key in the local DataContainer after receiving a null response. > The problem can be reproduced with {{TxReadAfterLosingOwnershipTest}} and its subclasses, by replacing the {{operation.update(cache(1));}} line with {{operation.update(cache(0));}} -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4464) Unify test suite for remote and embedded DSL based query tests

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4464?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4464: ----------------------------------------------- Roman Macor <rmacor(a)redhat.com> changed the Status of [bug 1160235|https://bugzilla.redhat.com/show_bug.cgi?id=1160235] from ON_QA to VERIFIED > Unify test suite for remote and embedded DSL based query tests > -------------------------------------------------------------- > > Key: ISPN-4464 > URL: https://issues.jboss.org/browse/ISPN-4464 > Project: Infinispan > Issue Type: Task > Components: Test Suite - Query > Affects Versions: 7.0.0.Alpha4 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4998) Infinispan 7 MapReduce giving inconsistent results

by Vijay Bhoomireddy (JIRA)

Vijay Bhoomireddy created ISPN-4998: --------------------------------------- Summary: Infinispan 7 MapReduce giving inconsistent results Key: ISPN-4998 URL: https://issues.jboss.org/browse/ISPN-4998 Project: Infinispan Issue Type: Bug Components: Distributed Execution and Map/Reduce Affects Versions: 7.0.0.Final Reporter: Vijay Bhoomireddy Hi, We are using Infinispan Map Reduce for processing our datasets that are spread across nodes in the cluster. We are seeing some surprising results when Infinispan 7 is used. To provide the context, our input data contains 10965 records. When Map Reduce from Infinispan 6.0.2 is used, both Mapper and Reducer are seeing 10965 records and are processing the same. However, with the same code and input data, Infinispan 7 MR gives different results for different invocations of the program. For one run, it gave output as 10902 records and the next run it gave 10872 records. Results seem inconsistent across invocations. Not sure is this is an issue with the version7 of the framework. Any help would be greatly appreciated. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 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 November 2014