March 2014 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-4145) Infinispan cluster configuration with distribution mode

by Vijay Chandra (JIRA)

Vijay Chandra created ISPN-4145: ----------------------------------- Summary: Infinispan cluster configuration with distribution mode Key: ISPN-4145 URL: https://issues.jboss.org/browse/ISPN-4145 Project: Infinispan Issue Type: Bug Components: Core Affects Versions: 5.3.0.Final Environment: OS: Linux, App server :JBoss EAP - Version 6.2.0.GA Infinispan version :5.3.0.Final Jgroups version :jgroups-3.3.1.Final Reporter: Vijay Chandra Assignee: Dan Berindei We have two web applications running on different machines on the same network. We have cache configuration file namely.ie. ecp-cluster-infinispan.xml on each of the instance. we tried of configure the infinispan cluster in distributed mode using jgroups in order to to retrieve/access the cache values two applications(each other). We used groups-udp.xml file for Jgroups configuration which is bundled with infinispan core. We are not able to retrieve the cache entries of one web application(one machine) on another web application (other machine). Note : No clustering of web applications. Distributed cache which allows Infinispan to scale linearly by defining a number of cluster-wide replicas for each cache entry. I am attaching the configuration files which are used to configure the infinispan in distributed mode. Is this a configuration issue or use case. -- 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

1
0
0 / 0

[JBoss JIRA] (ISPN-4074) Only include public API in JavaDoc

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4074?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4074: ----------------------------------------------- Misha H. Ali <mhusnain(a)redhat.com> changed the Status of [bug 1014655|https://bugzilla.redhat.com/show_bug.cgi?id=1014655] from ON_QA to ASSIGNED > Only include public API in JavaDoc > ---------------------------------- > > Key: ISPN-4074 > URL: https://issues.jboss.org/browse/ISPN-4074 > Project: Infinispan > Issue Type: Feature Request > Components: Build process, Documentation-Core > Affects Versions: 7.0.0.Alpha1 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 7.0.0.Alpha2 > > > Introduce a @public tag and a custom Doclet so that we can filter out non-public interfaces/classes from the Javadocs -- 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

1
0
0 / 0

[JBoss JIRA] (ISPN-3957) Preload with async cache store is not efficient

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-3957?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-3957: ----------------------------------------------- gsheldon(a)redhat.com changed the Status of [bug 1075061|https://bugzilla.redhat.com/show_bug.cgi?id=1075061] from NEW to VERIFIED > Preload with async cache store is not efficient > ----------------------------------------------- > > Key: ISPN-3957 > URL: https://issues.jboss.org/browse/ISPN-3957 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores > Affects Versions: 5.2.7.Final > Reporter: Mircea Markus > Assignee: Dan Berindei > Labels: 621 > Fix For: 5.2.8.Final, 7.0.0.Alpha1, 7.0.0.Final > > > Configuring on a AdvancedCacheLoader preload=true and asyn=true cause it to load each entry in the store in a loop, each entry being loaded through an store read. > This is caused by the way loadAll is implemented in the AsynLoader: in order to enforce consistency with whatever is in memory it does some special handling. The thing is, though, that we don't need this advanced async loader logic during the initial preload, as the async cache loader is empty. -- 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

1
0
0 / 0

[JBoss JIRA] (ISPN-3947) HotRod client keep trying recover connections to a failed cluster

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-3947?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-3947: ----------------------------------------------- gsheldon(a)redhat.com changed the Status of [bug 1075061|https://bugzilla.redhat.com/show_bug.cgi?id=1075061] from NEW to VERIFIED > HotRod client keep trying recover connections to a failed cluster > ----------------------------------------------------------------- > > Key: ISPN-3947 > URL: https://issues.jboss.org/browse/ISPN-3947 > Project: Infinispan > Issue Type: Feature Request > Components: Remote Protocols > Affects Versions: 6.0.1.Final, 7.0.0.Alpha1 > Reporter: Wolf-Dieter Fink > Assignee: Galder Zamarreño > Priority: Critical > Labels: 621, hotrod, hotrod-java-client > Fix For: 7.0.0.Alpha1, 7.0.0.Final > > > If an infinispan-server cluster is not longer reachable for some reason, i.e. network disconnect, the hot-rod client try to re-establish the lost connections. > The client library will retry this by a fixed calculation based on the max numbers of connections from the pool or 10 multiplied with the number of available servers. > This can lead in a very long time until the application can continue and react as it will wait for the read- or connect-timeout for each try. > To improve this behaviour there should be a configurable limit of retries per server and/or a timeout in total. > This will give the application the chance to handle a remote-cache failure and reply to the user instead of hanging for minutes (with the default settings) -- 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

1
0
0 / 0

[JBoss JIRA] (ISPN-3845) CACHE_MODE_LOCAL flag only works in primary owner for non-tx caches

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-3845?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-3845: ----------------------------------------------- gsheldon(a)redhat.com changed the Status of [bug 1075061|https://bugzilla.redhat.com/show_bug.cgi?id=1075061] from NEW to VERIFIED > CACHE_MODE_LOCAL flag only works in primary owner for non-tx caches > ------------------------------------------------------------------- > > Key: ISPN-3845 > URL: https://issues.jboss.org/browse/ISPN-3845 > Project: Infinispan > Issue Type: Bug > Affects Versions: 6.0.0.Final > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Labels: 621, testsuite_stability > Fix For: 7.0.0.Alpha1 > > > the flag is not forcing the EntryWrappingInterceptor to wrap the entry. the result is the entry will not be stored in the cache. > It's causing the random failures in: > {noformat} > HotRodReplicationTest.testReplicatedPutWithTopologyChanges > HotRod11ReplicationTest.testReplicatedPutWithTopologyChanges > HotRod12ReplicationTest.testReplicatedPutWithTopologyChanges > {noformat} -- 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

1
0
0 / 0

[JBoss JIRA] (ISPN-4144) Cleanly shutdown intermediate M/R cache

by Alan Field (JIRA)

[ https://issues.jboss.org/browse/ISPN-4144?page=com.atlassian.jira.plugin.... ] Alan Field commented on ISPN-4144: ---------------------------------- >From looking at DefaultRebalancePolicy.setRebalancingEnabled, it looks like rebalance is enabled or disabled for all caches: https://github.com/infinispan/infinispan/blob/master/core/src/main/java/o... > Cleanly shutdown intermediate M/R cache > --------------------------------------- > > Key: ISPN-4144 > URL: https://issues.jboss.org/browse/ISPN-4144 > Project: Infinispan > Issue Type: Feature Request > Reporter: Vladimir Blagojevic > Assignee: Vladimir Blagojevic > > For intermediate per task caches we simply remove that cache from cache manager. This operation is cluster wide but it still triggers rebalancing which in turn possibly creates logs that might raise false alarms for admins. Investigate if calling clear before removing cache from cache manager and/or disabling rebalancing for intermediate cache leads to a "cleaner" cache shutdown. -- 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

1
0
0 / 0

[JBoss JIRA] (ISPN-4144) Cleanly shutdown intermediate M/R cache

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-4144?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic edited comment on ISPN-4144 at 3/21/14 2:33 PM: -------------------------------------------------------------------- Ok, I was recommend on our IRC chat that clear() would do what I wanted. There is a way to disable rebalancing but that call is only available through JMX which is ok I guess but it is weird to call system internal function through JMX. [~dan.berindei] how can we call LocalTopologyManagerImpl#setRebalancingEnabled as this method is not available through LocalTopologyManager interface or should we even do it to being with? What are you suggestions here? was (Author: vblagojevic): Ok, I was recommend on our IRC chat that clear() would do what I wanted. There is a way to disable rebalancing but that call is only available through JMX which is ok I guess but it is weird to call system internal function through JMX. [~dan.berindei] how can we call LocalTopologyManagerImpl#setRebalancingEnabled as this method is not available through LocalTopologyManagerImpl interface or should we even do it to being with? What are you suggestions here? > Cleanly shutdown intermediate M/R cache > --------------------------------------- > > Key: ISPN-4144 > URL: https://issues.jboss.org/browse/ISPN-4144 > Project: Infinispan > Issue Type: Feature Request > Reporter: Vladimir Blagojevic > Assignee: Vladimir Blagojevic > > For intermediate per task caches we simply remove that cache from cache manager. This operation is cluster wide but it still triggers rebalancing which in turn possibly creates logs that might raise false alarms for admins. Investigate if calling clear before removing cache from cache manager and/or disabling rebalancing for intermediate cache leads to a "cleaner" cache shutdown. -- 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

1
0
0 / 0

[JBoss JIRA] (ISPN-4144) Cleanly shutdown intermediate M/R cache

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-4144?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic commented on ISPN-4144: ------------------------------------------- Ok, I was recommend on our forum that clear() would do what I wanted. There is a way to disable rebalancing but that call is only available through JMX which is ok I guess but it is weird to call system internal function through JMX internally. [~dan.berindei] how can we call LocalTopologyManagerImpl#setRebalancingEnabled as this method is not available through LocalTopologyManagerImpl interface or should we even do it to being with? What are you suggestions here? > Cleanly shutdown intermediate M/R cache > --------------------------------------- > > Key: ISPN-4144 > URL: https://issues.jboss.org/browse/ISPN-4144 > Project: Infinispan > Issue Type: Feature Request > Reporter: Vladimir Blagojevic > Assignee: Vladimir Blagojevic > > For intermediate per task caches we simply remove that cache from cache manager. This operation is cluster wide but it still triggers rebalancing which in turn possibly creates logs that might raise false alarms for admins. Investigate if calling clear before removing cache from cache manager and/or disabling rebalancing for intermediate cache leads to a "cleaner" cache shutdown. -- 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

1
0
0 / 0

[JBoss JIRA] (ISPN-4144) Cleanly shutdown intermediate M/R cache

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-4144?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic edited comment on ISPN-4144 at 3/21/14 2:32 PM: -------------------------------------------------------------------- Ok, I was recommend on our IRC chat that clear() would do what I wanted. There is a way to disable rebalancing but that call is only available through JMX which is ok I guess but it is weird to call system internal function through JMX internally. [~dan.berindei] how can we call LocalTopologyManagerImpl#setRebalancingEnabled as this method is not available through LocalTopologyManagerImpl interface or should we even do it to being with? What are you suggestions here? was (Author: vblagojevic): Ok, I was recommend on our forum that clear() would do what I wanted. There is a way to disable rebalancing but that call is only available through JMX which is ok I guess but it is weird to call system internal function through JMX internally. [~dan.berindei] how can we call LocalTopologyManagerImpl#setRebalancingEnabled as this method is not available through LocalTopologyManagerImpl interface or should we even do it to being with? What are you suggestions here? > Cleanly shutdown intermediate M/R cache > --------------------------------------- > > Key: ISPN-4144 > URL: https://issues.jboss.org/browse/ISPN-4144 > Project: Infinispan > Issue Type: Feature Request > Reporter: Vladimir Blagojevic > Assignee: Vladimir Blagojevic > > For intermediate per task caches we simply remove that cache from cache manager. This operation is cluster wide but it still triggers rebalancing which in turn possibly creates logs that might raise false alarms for admins. Investigate if calling clear before removing cache from cache manager and/or disabling rebalancing for intermediate cache leads to a "cleaner" cache shutdown. -- 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

1
0
0 / 0

[JBoss JIRA] (ISPN-4144) Cleanly shutdown intermediate M/R cache

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-4144?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic edited comment on ISPN-4144 at 3/21/14 2:33 PM: -------------------------------------------------------------------- Ok, I was recommend on our IRC chat that clear() would do what I wanted. There is a way to disable rebalancing but that call is only available through JMX which is ok I guess but it is weird to call system internal function through JMX. [~dan.berindei] how can we call LocalTopologyManagerImpl#setRebalancingEnabled as this method is not available through LocalTopologyManagerImpl interface or should we even do it to being with? What are you suggestions here? was (Author: vblagojevic): Ok, I was recommend on our IRC chat that clear() would do what I wanted. There is a way to disable rebalancing but that call is only available through JMX which is ok I guess but it is weird to call system internal function through JMX internally. [~dan.berindei] how can we call LocalTopologyManagerImpl#setRebalancingEnabled as this method is not available through LocalTopologyManagerImpl interface or should we even do it to being with? What are you suggestions here? > Cleanly shutdown intermediate M/R cache > --------------------------------------- > > Key: ISPN-4144 > URL: https://issues.jboss.org/browse/ISPN-4144 > Project: Infinispan > Issue Type: Feature Request > Reporter: Vladimir Blagojevic > Assignee: Vladimir Blagojevic > > For intermediate per task caches we simply remove that cache from cache manager. This operation is cluster wide but it still triggers rebalancing which in turn possibly creates logs that might raise false alarms for admins. Investigate if calling clear before removing cache from cache manager and/or disabling rebalancing for intermediate cache leads to a "cleaner" cache shutdown. -- 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

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues March 2014