April 2015 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-5401) Align server and embedded exposed management properties

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5401?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5401: ----------------------------------------------- Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1210176|https://bugzilla.redhat.com/show_bug.cgi?id=1210176] from POST to MODIFIED > Align server and embedded exposed management properties > ------------------------------------------------------- > > Key: ISPN-5401 > URL: https://issues.jboss.org/browse/ISPN-5401 > Project: Infinispan > Issue Type: Enhancement > Components: JMX, reporting and management > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 7.2.0.Final > > > Server exposes more attributes than embedded, causing some confusion amongst our users, e.g. isCoordinator. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5421) Cache mode defined in default cache is not propagated to named cache

by Mark K (JIRA)

[ https://issues.jboss.org/browse/ISPN-5421?page=com.atlassian.jira.plugin.... ] Mark K updated ISPN-5421: ------------------------- Steps to Reproduce: {quote} <cache-container default-cache="default-dist" statistics="true" shutdown-hook="DEFAULT"> <jmx domain="org.infinispan"/> <transport stack="tcp"/>  <distributed-cache name="default-dist" mode="ASYNC" owners="2" segments="120" deadlock-detection-spin="3000" unreliable-return-values="true" statistics="true"/> <distributed-cache name="myNamedCache"/> </cache-container> {quote} The "myNamedCache" will be SYNC, even though the default cache is ASYNC. was: {{ <cache-container default-cache="default-dist" statistics="true" shutdown-hook="DEFAULT"> <jmx domain="org.infinispan"/> <transport stack="tcp"/>  <distributed-cache name="default-dist" mode="ASYNC" owners="2" segments="120" deadlock-detection-spin="3000" unreliable-return-values="true" statistics="true"/> <distributed-cache name="myNamedCache"/> </cache-container> }} The "myNamedCache" will be SYNC, even though the default cache is ASYNC. > Cache mode defined in default cache is not propagated to named cache > -------------------------------------------------------------------- > > Key: ISPN-5421 > URL: https://issues.jboss.org/browse/ISPN-5421 > Project: Infinispan > Issue Type: Bug > Components: Configuration > Affects Versions: 7.1.1.Final > Environment: Linux, Java 1.7.0_55 > Reporter: Mark K > Labels: cachemode, configuration > > The cache mode (SYNC/ASYNC) is not propagated from the default-cache configuration to the named cache and defaults to SYNC, even when default-cache is set to ASYNC. > Example Config: -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5421) Cache mode defined in default cache is not propagated to named cache

by Mark K (JIRA)

Mark K created ISPN-5421: ---------------------------- Summary: Cache mode defined in default cache is not propagated to named cache Key: ISPN-5421 URL: https://issues.jboss.org/browse/ISPN-5421 Project: Infinispan Issue Type: Bug Components: Configuration Affects Versions: 7.1.1.Final Environment: Linux, Java 1.7.0_55 Reporter: Mark K The cache mode (SYNC/ASYNC) is not propagated from the default-cache configuration to the named cache and defaults to SYNC, even when default-cache is set to ASYNC. Example Config: -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

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

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4999?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4999: ----------------------------------------------- Dave Stahl <dstahl(a)redhat.com> changed the Status of [bug 1214694|https://bugzilla.redhat.com/show_bug.cgi?id=1214694] from POST to MODIFIED > 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.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5420) Thread pools are depleted by ClusterTopologyManagerImpl.waitForView() and causing deadlock

by Dan Berindei (JIRA)

Dan Berindei created ISPN-5420: ---------------------------------- Summary: Thread pools are depleted by ClusterTopologyManagerImpl.waitForView() and causing deadlock Key: ISPN-5420 URL: https://issues.jboss.org/browse/ISPN-5420 Project: Infinispan Issue Type: Bug Components: Core Affects Versions: 7.1.1.Final, 6.0.2.Final Reporter: Dan Berindei Assignee: Dan Berindei Fix For: 7.2.0.Final The join process was designed in the idea that a node would start its caches in sequential order, so {{ClusterTopologyManager.waitForView()}} would block at most once for each joining node. However, WildFly actually starts {{2 * Runtime.availableProcessors()}} caches in parallel, and this can be a problem when the machine has a lot of cores and multiple nodes. {{ClustertopologyManager.handleClusterView()}} only updates the {{viewId}} after it updated the cache topologies of each cache AND after it confirmed the availability of all the nodes with a {{POLICY_GET_STATUS}} RPC. This RPC can block, and it's very easy for the remote-executor thread pool on the coordinator to become overloades with threads like this: {noformat} "remote-thread-172" daemon prio=10 tid=0x00007f0cc48c0000 nid=0x28ca4 in Object.wait() [0x00007f0c5f25b000] java.lang.Thread.State: TIMED_WAITING (on object monitor) at java.lang.Object.wait(Native Method) at org.infinispan.topology.ClusterTopologyManagerImpl.waitForView(ClusterTopologyManagerImpl.java:357) - locked <0x00000000ff3bd900> (a java.lang.Object) at org.infinispan.topology.ClusterTopologyManagerImpl.handleJoin(ClusterTopologyManagerImpl.java:123) at org.infinispan.topology.CacheTopologyControlCommand.doPerform(CacheTopologyControlCommand.java:162) at org.infinispan.topology.CacheTopologyControlCommand.perform(CacheTopologyControlCommand.java:144) at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher$4.run(CommandAwareRpcDispatcher.java:276) {noformat} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5420) Thread pools are depleted by ClusterTopologyManagerImpl.waitForView() and causing deadlock

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-5420?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-5420: ------------------------------- Priority: Critical (was: Major) > Thread pools are depleted by ClusterTopologyManagerImpl.waitForView() and causing deadlock > ------------------------------------------------------------------------------------------ > > Key: ISPN-5420 > URL: https://issues.jboss.org/browse/ISPN-5420 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 6.0.2.Final, 7.1.1.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Critical > Fix For: 7.2.0.Final > > > The join process was designed in the idea that a node would start its caches in sequential order, so {{ClusterTopologyManager.waitForView()}} would block at most once for each joining node. However, WildFly actually starts {{2 * Runtime.availableProcessors()}} caches in parallel, and this can be a problem when the machine has a lot of cores and multiple nodes. > {{ClustertopologyManager.handleClusterView()}} only updates the {{viewId}} after it updated the cache topologies of each cache AND after it confirmed the availability of all the nodes with a {{POLICY_GET_STATUS}} RPC. This RPC can block, and it's very easy for the remote-executor thread pool on the coordinator to become overloades with threads like this: > {noformat} > "remote-thread-172" daemon prio=10 tid=0x00007f0cc48c0000 nid=0x28ca4 in Object.wait() [0x00007f0c5f25b000] > java.lang.Thread.State: TIMED_WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > at org.infinispan.topology.ClusterTopologyManagerImpl.waitForView(ClusterTopologyManagerImpl.java:357) > - locked <0x00000000ff3bd900> (a java.lang.Object) > at org.infinispan.topology.ClusterTopologyManagerImpl.handleJoin(ClusterTopologyManagerImpl.java:123) > at org.infinispan.topology.CacheTopologyControlCommand.doPerform(CacheTopologyControlCommand.java:162) > at org.infinispan.topology.CacheTopologyControlCommand.perform(CacheTopologyControlCommand.java:144) > at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher$4.run(CommandAwareRpcDispatcher.java:276) > {noformat} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5420) Thread pools are depleted by ClusterTopologyManagerImpl.waitForView() and causing deadlock

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-5420?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-5420: ------------------------------- Status: Open (was: New) > Thread pools are depleted by ClusterTopologyManagerImpl.waitForView() and causing deadlock > ------------------------------------------------------------------------------------------ > > Key: ISPN-5420 > URL: https://issues.jboss.org/browse/ISPN-5420 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 6.0.2.Final, 7.1.1.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Critical > Fix For: 7.2.0.Final > > > The join process was designed in the idea that a node would start its caches in sequential order, so {{ClusterTopologyManager.waitForView()}} would block at most once for each joining node. However, WildFly actually starts {{2 * Runtime.availableProcessors()}} caches in parallel, and this can be a problem when the machine has a lot of cores and multiple nodes. > {{ClustertopologyManager.handleClusterView()}} only updates the {{viewId}} after it updated the cache topologies of each cache AND after it confirmed the availability of all the nodes with a {{POLICY_GET_STATUS}} RPC. This RPC can block, and it's very easy for the remote-executor thread pool on the coordinator to become overloades with threads like this: > {noformat} > "remote-thread-172" daemon prio=10 tid=0x00007f0cc48c0000 nid=0x28ca4 in Object.wait() [0x00007f0c5f25b000] > java.lang.Thread.State: TIMED_WAITING (on object monitor) > at java.lang.Object.wait(Native Method) > at org.infinispan.topology.ClusterTopologyManagerImpl.waitForView(ClusterTopologyManagerImpl.java:357) > - locked <0x00000000ff3bd900> (a java.lang.Object) > at org.infinispan.topology.ClusterTopologyManagerImpl.handleJoin(ClusterTopologyManagerImpl.java:123) > at org.infinispan.topology.CacheTopologyControlCommand.doPerform(CacheTopologyControlCommand.java:162) > at org.infinispan.topology.CacheTopologyControlCommand.perform(CacheTopologyControlCommand.java:144) > at org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher$4.run(CommandAwareRpcDispatcher.java:276) > {noformat} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5401) Align server and embedded exposed management properties

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5401?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5401: ----------------------------------------------- Tristan Tarrant <ttarrant(a)redhat.com> changed the Status of [bug 1210176|https://bugzilla.redhat.com/show_bug.cgi?id=1210176] from ASSIGNED to POST > Align server and embedded exposed management properties > ------------------------------------------------------- > > Key: ISPN-5401 > URL: https://issues.jboss.org/browse/ISPN-5401 > Project: Infinispan > Issue Type: Enhancement > Components: JMX, reporting and management > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 7.2.0.Final > > > Server exposes more attributes than embedded, causing some confusion amongst our users, e.g. isCoordinator. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5264) Optimize PutAll operations (library mode)

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5264?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5264: ----------------------------------------------- William Burns <wburns(a)redhat.com> changed the Status of [bug 1213367|https://bugzilla.redhat.com/show_bug.cgi?id=1213367] from ASSIGNED to POST > Optimize PutAll operations (library mode) > ----------------------------------------- > > Key: ISPN-5264 > URL: https://issues.jboss.org/browse/ISPN-5264 > Project: Infinispan > Issue Type: Enhancement > Reporter: Pedro Zapata > Assignee: William Burns > Fix For: 7.2.0.CR1, 7.2.0.Final > > > - PutAll: to ensure that users can load massive amount of data into the grid quickly in Library mode > - Performance improvement over large data sets. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5266) Optimize PutAll operations (Hot Rod)

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5266?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5266: ----------------------------------------------- William Burns <wburns(a)redhat.com> changed the Status of [bug 1213367|https://bugzilla.redhat.com/show_bug.cgi?id=1213367] from ASSIGNED to POST > Optimize PutAll operations (Hot Rod) > ------------------------------------ > > Key: ISPN-5266 > URL: https://issues.jboss.org/browse/ISPN-5266 > Project: Infinispan > Issue Type: Enhancement > Reporter: Pedro Zapata > Assignee: William Burns > Fix For: 7.2.0.CR1, 7.2.0.Final > > > - PutAll: to ensure that users can load massive amount of data into the grid quickly over Hot Rod. > - Performance improvement over large data sets. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues April 2015