April 2015 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-5351) read()ing protected Attributes should support user-supplied copying methods

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5351?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-5351: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/3363 > read()ing protected Attributes should support user-supplied copying methods > --------------------------------------------------------------------------- > > Key: ISPN-5351 > URL: https://issues.jboss.org/browse/ISPN-5351 > Project: Infinispan > Issue Type: Bug > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > > Cloning a configuration attribute sometimes is not enough. For example when dealing with collections and immutable types we need to overcome the following: > Caused by: java.lang.UnsupportedOperationException > at org.infinispan.commons.util.Immutables$ImmutableTypedProperties.put(Immutables.java:622) > at org.infinispan.configuration.cache.IndexingConfigurationBuilder.setProperty(IndexingConfigurationBuilder.java:130) > at org.infinispan.configuration.cache.IndexingConfigurationBuilder.addProperty(IndexingConfigurationBuilder.java:107) > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5351) read()ing protected Attributes should support user-supplied copying methods

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5351?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-5351: ---------------------------------- Status: Open (was: New) > read()ing protected Attributes should support user-supplied copying methods > --------------------------------------------------------------------------- > > Key: ISPN-5351 > URL: https://issues.jboss.org/browse/ISPN-5351 > Project: Infinispan > Issue Type: Bug > Reporter: Tristan Tarrant > > Cloning a configuration attribute sometimes is not enough. For example when dealing with collections and immutable types we need to overcome the following: > Caused by: java.lang.UnsupportedOperationException > at org.infinispan.commons.util.Immutables$ImmutableTypedProperties.put(Immutables.java:622) > at org.infinispan.configuration.cache.IndexingConfigurationBuilder.setProperty(IndexingConfigurationBuilder.java:130) > at org.infinispan.configuration.cache.IndexingConfigurationBuilder.addProperty(IndexingConfigurationBuilder.java:107) > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5353) CacheNotifierImpl component is started/stopped twice because it is both a CacheNotifier and a ClusterCacheNotifier component

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-5353?page=com.atlassian.jira.plugin.... ] Adrian Nistor commented on ISPN-5353: ------------------------------------- This issue was not noticed because duplicated start/stop was mostly harmless. > CacheNotifierImpl component is started/stopped twice because it is both a CacheNotifier and a ClusterCacheNotifier component > ---------------------------------------------------------------------------------------------------------------------------- > > Key: ISPN-5353 > URL: https://issues.jboss.org/browse/ISPN-5353 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 7.2.0.Beta2 > Reporter: Adrian Nistor > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5353) CacheNotifierImpl component is started/stopped twice because it is is both a CacheNotifier and a ClusterCacheNotifier component

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-5353?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-5353: -------------------------------- Affects Version/s: 7.2.0.Beta2 Component/s: Core > CacheNotifierImpl component is started/stopped twice because it is is both a CacheNotifier and a ClusterCacheNotifier component > ------------------------------------------------------------------------------------------------------------------------------- > > Key: ISPN-5353 > URL: https://issues.jboss.org/browse/ISPN-5353 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 7.2.0.Beta2 > Reporter: Adrian Nistor > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5353) CacheNotifierImpl component is started/stopped twice because it is both a CacheNotifier and a ClusterCacheNotifier component

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-5353?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-5353: -------------------------------- Summary: CacheNotifierImpl component is started/stopped twice because it is both a CacheNotifier and a ClusterCacheNotifier component (was: CacheNotifierImpl component is started/stopped twice because it is is both a CacheNotifier and a ClusterCacheNotifier component) > CacheNotifierImpl component is started/stopped twice because it is both a CacheNotifier and a ClusterCacheNotifier component > ---------------------------------------------------------------------------------------------------------------------------- > > Key: ISPN-5353 > URL: https://issues.jboss.org/browse/ISPN-5353 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 7.2.0.Beta2 > Reporter: Adrian Nistor > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5353) CacheNotifierImpl component is started/stopped twice because it is is both a CacheNotifier and a ClusterCacheNotifier component

by Adrian Nistor (JIRA)

Adrian Nistor created ISPN-5353: ----------------------------------- Summary: CacheNotifierImpl component is started/stopped twice because it is is both a CacheNotifier and a ClusterCacheNotifier component Key: ISPN-5353 URL: https://issues.jboss.org/browse/ISPN-5353 Project: Infinispan Issue Type: Bug Reporter: Adrian Nistor -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5159) Make concurrent startup smooth

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-5159?page=com.atlassian.jira.plugin.... ] Dan Berindei commented on ISPN-5159: ------------------------------------ [~rvansa] I wasn't thinking about requiring changes to the JGroups configuration either, my thinking was that the default configuration should be good enough to avoid merges during startup. I don't think all the internal caches can be recreated on the fly: e.g. the cluster registry cache is created by core and then used by other components like query, we'd need both a way to notify the cluster registry to rebuild the cache, and a way for the cluster registry to tell all the components that they need to rebuild their slice of the cluster registry cache (assuming that those components do have the necessary information). > Make concurrent startup smooth > ------------------------------ > > Key: ISPN-5159 > URL: https://issues.jboss.org/browse/ISPN-5159 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Affects Versions: 7.1.0.Beta1 > Reporter: Radim Vansa > Assignee: Dan Berindei > > When starting many instances in parallel, it often happens that the node does not detect its neighborhood very well and this results in many subclusters, merging views etc. > Merging two available partitions has undefined results (AFAIK). While we can expect that there are no requests to the cluster from the application ^1^, Infinispan itself uses some caches to store internal information (HotRod routing, Protobuf etc...). It would be better if the available-available merge would provide hooks for rebuilding this info. > ^1^) Being able to start the cluster with reads/writes disabled and enable them only when the cache has expected number of members would be convenient, too. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5159) Make concurrent startup smooth

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-5159?page=com.atlassian.jira.plugin.... ] Dan Berindei commented on ISPN-5159: ------------------------------------ One more question... I was expecting merges during startup to be much less of a problem since JGRP-1899 was fixed. [~rvansa] [~mcimbora] are you still seeing merges during startup with JGroups 3.6.1+? > Make concurrent startup smooth > ------------------------------ > > Key: ISPN-5159 > URL: https://issues.jboss.org/browse/ISPN-5159 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Affects Versions: 7.1.0.Beta1 > Reporter: Radim Vansa > Assignee: Dan Berindei > > When starting many instances in parallel, it often happens that the node does not detect its neighborhood very well and this results in many subclusters, merging views etc. > Merging two available partitions has undefined results (AFAIK). While we can expect that there are no requests to the cluster from the application ^1^, Infinispan itself uses some caches to store internal information (HotRod routing, Protobuf etc...). It would be better if the available-available merge would provide hooks for rebuilding this info. > ^1^) Being able to start the cluster with reads/writes disabled and enable them only when the cache has expected number of members would be convenient, too. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5352) Improve scalability of DSL based filters by using the publish/subscribe feature of org.infinispan.objectfilter.Matcher

by Adrian Nistor (JIRA)

Adrian Nistor created ISPN-5352: ----------------------------------- Summary: Improve scalability of DSL based filters by using the publish/subscribe feature of org.infinispan.objectfilter.Matcher Key: ISPN-5352 URL: https://issues.jboss.org/browse/ISPN-5352 Project: Infinispan Issue Type: Bug Components: Listeners Affects Versions: 7.2.0.Beta2 Reporter: Adrian Nistor Assignee: Adrian Nistor Fix For: 7.2.0.CR1, 7.2.0.Final org.infinispan.objectfilter.Matcher is able to index multiple filters and use a publish/subscribe model that is more efficient than using the org.infinispan.objectfilter.ObjectFilter which would execute each filter serially. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5352) Improve scalability of DSL based filters by using the publish/subscribe feature of org.infinispan.objectfilter.Matcher

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-5352?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-5352: -------------------------------- Status: Open (was: New) > Improve scalability of DSL based filters by using the publish/subscribe feature of org.infinispan.objectfilter.Matcher > ----------------------------------------------------------------------------------------------------------------------- > > Key: ISPN-5352 > URL: https://issues.jboss.org/browse/ISPN-5352 > Project: Infinispan > Issue Type: Bug > Components: Listeners > Affects Versions: 7.2.0.Beta2 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.2.0.CR1, 7.2.0.Final > > > org.infinispan.objectfilter.Matcher is able to index multiple filters and use a publish/subscribe model that is more efficient than using the org.infinispan.objectfilter.ObjectFilter which would execute each filter serially. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 6 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues April 2015