February 2017 - infinispan-issues

[JBoss JIRA] (ISPN-6346) Zipkin based cluster-wide request tracing

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6346?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6346: ---------------------------------- Fix Version/s: (was: 9.0.0.Final) > Zipkin based cluster-wide request tracing > ----------------------------------------- > > Key: ISPN-6346 > URL: https://issues.jboss.org/browse/ISPN-6346 > Project: Infinispan > Issue Type: Feature Request > Components: JMX, reporting and management > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Priority: Minor > > Zipkin (http://zipkin.io) is a distributed tracing system that started at Twitter. > Infinispan should integrate with it so that we can trace individual cache requests in terms of which components it touches and how long it takes in each, and also when the cache requests end up going to other nodes (plus see which remote components it touches). > The idea is that this should give us a better idea of what a particular operation does in terms of how many nodes it goes to, and what it does in each. This would be hugely beneficial to be able to better analyse performance issues. > A key advantage of Zipkin is that it can be run in production since it can be configured to only track a fraction of all requests, making it even more valuable from the monitoring POV. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6340) Expose indexing statistics via DMR

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6340?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6340: ---------------------------------- Fix Version/s: (was: 9.0.0.Final) (was: 9.0.0.CR3) > Expose indexing statistics via DMR > ---------------------------------- > > Key: ISPN-6340 > URL: https://issues.jboss.org/browse/ISPN-6340 > Project: Infinispan > Issue Type: Feature Request > Components: JMX, reporting and management > Reporter: Adrian Nistor > Assignee: Gustavo Fernandes > > It would be great to have status about progress and size of the index as well! Is index in healthy, is it broken, does it need rebuilding? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7314) Remove duplication code in AbstractListenerImpl and CacheNotifierImpl

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7314?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7314: ---------------------------------- Fix Version/s: (was: 9.0.0.Final) > Remove duplication code in AbstractListenerImpl and CacheNotifierImpl > --------------------------------------------------------------------- > > Key: ISPN-7314 > URL: https://issues.jboss.org/browse/ISPN-7314 > Project: Infinispan > Issue Type: Enhancement > Affects Versions: 9.0.0.Beta2 > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > > To speed up introduction of addFilteredListener, some code was duplicated in AbstractListenerImpl and CacheNotifierImpl. Refactor/deduplicate code. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6494) Investigate bundler performance

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-6494?page=com.atlassian.jira.plugin.... ] Dan Berindei commented on ISPN-6494: ------------------------------------ JGroups 4.0 no longer has {{sender-sends-with-timer}}, but {{no-bundler}} (the equivalent of {{sender-sends-with-timer}} + {{DONT_BUNDLE}}) is still much better than {{transfer-queue}} in some tests. > Investigate bundler performance > ------------------------------- > > Key: ISPN-6494 > URL: https://issues.jboss.org/browse/ISPN-6494 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 9.0.0.Alpha1 > Reporter: Dan Berindei > Assignee: Dan Berindei > > For ISPN-6027 we changed the default JGroups bundler to {{sender-sends-with-timer}}, because it was faster in some of the performance tests. However, IspnPerfTest shows {{transfer-queue-bundler}} to be consistently better, so we need to investigate the bundler choice again. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6494) Investigate bundler performance

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6494?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6494: ---------------------------------- Fix Version/s: (was: 9.0.0.Final) (was: 9.0.0.Alpha2) > Investigate bundler performance > ------------------------------- > > Key: ISPN-6494 > URL: https://issues.jboss.org/browse/ISPN-6494 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 9.0.0.Alpha1 > Reporter: Dan Berindei > Assignee: Dan Berindei > > For ISPN-6027 we changed the default JGroups bundler to {{sender-sends-with-timer}}, because it was faster in some of the performance tests. However, IspnPerfTest shows {{transfer-queue-bundler}} to be consistently better, so we need to investigate the bundler choice again. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6994) Introduce an AdvancedCache.as(Subject) method for explicit authorization

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6994?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6994: ---------------------------------- Fix Version/s: (was: 9.0.0.Final) > Introduce an AdvancedCache.as(Subject) method for explicit authorization > ------------------------------------------------------------------------ > > Key: ISPN-6994 > URL: https://issues.jboss.org/browse/ISPN-6994 > Project: Infinispan > Issue Type: Feature Request > Components: Core, Security > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Labels: performance > > Currently the subject is extracted either from the AccessControlContext or from the lightweight security implementation (which uses a ThreadLocal). > Both of these approaches have fairly high costs, so we should, if possible, use an explicit Subject. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7475) Fixes for Hibernate 2LC integration with Infinispan 9

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7475?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7475: ---------------------------------- Priority: Critical (was: Blocker) > Fixes for Hibernate 2LC integration with Infinispan 9 > ----------------------------------------------------- > > Key: ISPN-7475 > URL: https://issues.jboss.org/browse/ISPN-7475 > Project: Infinispan > Issue Type: Bug > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Priority: Critical > Fix For: 9.1.0.Final > > > Umbrella JIRA for all issues found when integrating Hibernate 2LC with Infinispan 9. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7475) Fixes for Hibernate 2LC integration with Infinispan 9

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7475?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7475: ---------------------------------- Fix Version/s: 9.1.0.Final (was: 9.0.0.Final) > Fixes for Hibernate 2LC integration with Infinispan 9 > ----------------------------------------------------- > > Key: ISPN-7475 > URL: https://issues.jboss.org/browse/ISPN-7475 > Project: Infinispan > Issue Type: Bug > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Priority: Critical > Fix For: 9.1.0.Final > > > Umbrella JIRA for all issues found when integrating Hibernate 2LC with Infinispan 9. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6478) Netty worker thread starvation with events

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6478?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6478: ---------------------------------- Priority: Critical (was: Blocker) > Netty worker thread starvation with events > ------------------------------------------ > > Key: ISPN-6478 > URL: https://issues.jboss.org/browse/ISPN-6478 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 8.2.1.Final > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Priority: Critical > > As a result of ISPN-6005, we decoupled the incoming Hot Rod server invocations from sending events by adding a intermediate queue that maintains the events to send to clients. However, this separation can lead to a Netty worker thread starvation issue since we add the events to the queue in Netty's IO thread, so if the queue is full, incoming requests are stuck. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6478) Netty worker thread starvation with events

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6478?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6478: ---------------------------------- Fix Version/s: (was: 9.0.0.Final) (was: 9.0.0.CR3) > Netty worker thread starvation with events > ------------------------------------------ > > Key: ISPN-6478 > URL: https://issues.jboss.org/browse/ISPN-6478 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 8.2.1.Final > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Priority: Blocker > > As a result of ISPN-6005, we decoupled the incoming Hot Rod server invocations from sending events by adding a intermediate queue that maintains the events to send to clients. However, this separation can lead to a Netty worker thread starvation issue since we add the events to the queue in Netty's IO thread, so if the queue is full, incoming requests are stuck. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues February 2017