February 2016 - infinispan-issues

[JBoss JIRA] (ISPN-6195) CacheNotFoundResponse error when starting multiple Infinispan Server instances in parallel

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-6195?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-6195: ----------------------------------- Description: Starting two clustered Infinispan Server instances in parallel throws CacheNotFoundResponse exception in one of the nodes with the other not showing any other exceptions/errors: {code} 08:52:46,152 ERROR [org.infinispan.topology.ClusterTopologyManagerImpl] (transport-thread--p4-t1) ISPN000196: Failed to recover cluster state after the current node became the coordinator: org.infinispan.commons.CacheException: Unsuccessful response received from node node2: CacheNotFoundResponse at org.infinispan.topology.ClusterTopologyManagerImpl.executeOnClusterSync(ClusterTopologyManagerImpl.java:529) at org.infinispan.topology.ClusterTopologyManagerImpl.recoverClusterStatus(ClusterTopologyManagerImpl.java:387) at org.infinispan.topology.ClusterTopologyManagerImpl.handleClusterView(ClusterTopologyManagerImpl.java:321) at org.infinispan.topology.ClusterTopologyManagerImpl.lambda$start$133(ClusterTopologyManagerImpl.java:131) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at org.infinispan.executors.SemaphoreCompletionService$QueueingTask.runInternal(SemaphoreCompletionService.java:173) at org.infinispan.executors.SemaphoreCompletionService$QueueingTask.run(SemaphoreCompletionService.java:151) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) {code} was: Starting two clustered Infinispan Server instances in parallel throws CacheNotFoundResponse exception in one of the nodes with the other not showing any other exceptions/errors: {code} 08:52:46,152 ERROR [org.infinispan.topology.ClusterTopologyManagerImpl] (transport-thread--p4-t1) ISPN000196: Failed to recover cluster state after the current node became the coordinator: org.infinispan.commons.CacheException: Unsuccessful response received from node node2: CacheNotFoundResponse at org.infinispan.topology.ClusterTopologyManagerImpl.executeOnClusterSync(ClusterTopologyManagerImpl.java:529) at org.infinispan.topology.ClusterTopologyManagerImpl.recoverClusterStatus(ClusterTopologyManagerImpl.java:387) at org.infinispan.topology.ClusterTopologyManagerImpl.handleClusterView(ClusterTopologyManagerImpl.java:321) at org.infinispan.topology.ClusterTopologyManagerImpl.lambda$start$133(ClusterTopologyManagerImpl.java:131) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at org.infinispan.executors.SemaphoreCompletionService$QueueingTask.runInternal(SemaphoreCompletionService.java:173) at org.infinispan.executors.SemaphoreCompletionService$QueueingTask.run(SemaphoreCompletionService.java:151) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) {code} > CacheNotFoundResponse error when starting multiple Infinispan Server instances in parallel > ------------------------------------------------------------------------------------------ > > Key: ISPN-6195 > URL: https://issues.jboss.org/browse/ISPN-6195 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 8.2.0.Beta1 > Reporter: Galder Zamarreño > Assignee: Pedro Ruivo > Fix For: 8.2.0.Final > > > Starting two clustered Infinispan Server instances in parallel throws CacheNotFoundResponse exception in one of the nodes with the other not showing any other exceptions/errors: > {code} > 08:52:46,152 ERROR [org.infinispan.topology.ClusterTopologyManagerImpl] (transport-thread--p4-t1) > ISPN000196: Failed to recover cluster state after the current node became the coordinator: > org.infinispan.commons.CacheException: Unsuccessful response received from node node2: > CacheNotFoundResponse > at org.infinispan.topology.ClusterTopologyManagerImpl.executeOnClusterSync(ClusterTopologyManagerImpl.java:529) > at org.infinispan.topology.ClusterTopologyManagerImpl.recoverClusterStatus(ClusterTopologyManagerImpl.java:387) > at org.infinispan.topology.ClusterTopologyManagerImpl.handleClusterView(ClusterTopologyManagerImpl.java:321) > at org.infinispan.topology.ClusterTopologyManagerImpl.lambda$start$133(ClusterTopologyManagerImpl.java:131) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at org.infinispan.executors.SemaphoreCompletionService$QueueingTask.runInternal(SemaphoreCompletionService.java:173) > at org.infinispan.executors.SemaphoreCompletionService$QueueingTask.run(SemaphoreCompletionService.java:151) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6194) Capture error text in JSON response for failed DMR ops

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-6194?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic reassigned ISPN-6194: ----------------------------------------- Assignee: Vladimir Blagojevic > Capture error text in JSON response for failed DMR ops > ------------------------------------------------------ > > Key: ISPN-6194 > URL: https://issues.jboss.org/browse/ISPN-6194 > Project: Infinispan > Issue Type: Enhancement > Components: Console > Affects Versions: 8.1.0.Final > Reporter: Vladimir Blagojevic > Assignee: Vladimir Blagojevic > > We do not currently capture error text from failed DMR ops. We should grab the error text and pass it to resulting promise and potentially use this text in error logs and console UI -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6194) Capture error text in JSON response for failed DMR ops

by Vladimir Blagojevic (JIRA)

Vladimir Blagojevic created ISPN-6194: ----------------------------------------- Summary: Capture error text in JSON response for failed DMR ops Key: ISPN-6194 URL: https://issues.jboss.org/browse/ISPN-6194 Project: Infinispan Issue Type: Enhancement Components: Console Affects Versions: 8.1.0.Final Reporter: Vladimir Blagojevic We do not currently capture error text from failed DMR ops. We should grab the error text and pass it to resulting promise and potentially use this text in error logs and console UI -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6056) Improve ReplicableCommand marshalling

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6056?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6056: ---------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 8.2.0.Beta2 8.2.0.Final Resolution: Done > Improve ReplicableCommand marshalling > ------------------------------------- > > Key: ISPN-6056 > URL: https://issues.jboss.org/browse/ISPN-6056 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Affects Versions: 8.0.2.Final > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Fix For: 8.2.0.Beta2, 8.2.0.Final > > > Memory-wise speaking, it is possible to reduce the pressure when (un)marshalling the ReplicableCommand by doing it directly in the ObjectInput/ObjectOutput. > Improvements: > * remove Object array created by get/setParameters() > * remove byte array creating in the externalizer. > Public API change: > * ReplicableCommand interface: deprecate get/setParameters() and create readFrom()/writeTo() methods. > * Marshaller interface: added new start... methods. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-4953) Review quickstart README metadata to optimize it for the Google search

by Martin Gencur (JIRA)

[ https://issues.jboss.org/browse/ISPN-4953?page=com.atlassian.jira.plugin.... ] Martin Gencur updated ISPN-4953: -------------------------------- Status: Open (was: New) > Review quickstart README metadata to optimize it for the Google search > ---------------------------------------------------------------------- > > Key: ISPN-4953 > URL: https://issues.jboss.org/browse/ISPN-4953 > Project: Infinispan > Issue Type: Bug > Components: Demos and Tutorials > Reporter: Sande Gilda > Assignee: Martin Gencur > > See JDF-787. > The jboss.org development team plans to do the following: > - Parse the first line of each README file to remove the quickstart name prefix and use the rest for Google SEO title. That field is limited to ~55 characters. > - Use the 'Summary:' metadata for the description. This field is limited to 155 characters. > This information is what shows up on the search result page, so the better it better describes the example. > I went through all the JBoss EAP quickstart README files to shorten the title and lengthen the Summary to be more descriptive. We need to do this for all of the other quickstarts, including: > * JDG: https://github.com/jboss-developer/jboss-jdg-quickstarts > See related JBoss EAP bugs for details: > * https://bugzilla.redhat.com/show_bug.cgi?id=1160776 > * https://bugzilla.redhat.com/show_bug.cgi?id=1159374 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-4953) Review quickstart README metadata to optimize it for the Google search

by Martin Gencur (JIRA)

[ https://issues.jboss.org/browse/ISPN-4953?page=com.atlassian.jira.plugin.... ] Martin Gencur updated ISPN-4953: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/jboss-developer/jboss-jdg-quickstarts/pull/118 > Review quickstart README metadata to optimize it for the Google search > ---------------------------------------------------------------------- > > Key: ISPN-4953 > URL: https://issues.jboss.org/browse/ISPN-4953 > Project: Infinispan > Issue Type: Bug > Components: Demos and Tutorials > Reporter: Sande Gilda > Assignee: Martin Gencur > > See JDF-787. > The jboss.org development team plans to do the following: > - Parse the first line of each README file to remove the quickstart name prefix and use the rest for Google SEO title. That field is limited to ~55 characters. > - Use the 'Summary:' metadata for the description. This field is limited to 155 characters. > This information is what shows up on the search result page, so the better it better describes the example. > I went through all the JBoss EAP quickstart README files to shorten the title and lengthen the Summary to be more descriptive. We need to do this for all of the other quickstarts, including: > * JDG: https://github.com/jboss-developer/jboss-jdg-quickstarts > See related JBoss EAP bugs for details: > * https://bugzilla.redhat.com/show_bug.cgi?id=1160776 > * https://bugzilla.redhat.com/show_bug.cgi?id=1159374 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6121) query-dsl server module must list jboss-logging dependency

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6121?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6121: ---------------------------------- Fix Version/s: 8.2.0.Final > query-dsl server module must list jboss-logging dependency > ---------------------------------------------------------- > > Key: ISPN-6121 > URL: https://issues.jboss.org/browse/ISPN-6121 > Project: Infinispan > Issue Type: Bug > Components: Server > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 8.2.0.Beta1, 8.2.0.Final, 8.1.2.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6174) Avoid calling the server after iteration is done in the remote iterator

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6174?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6174: ---------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 8.2.0.Final Resolution: Done > Avoid calling the server after iteration is done in the remote iterator > ----------------------------------------------------------------------- > > Key: ISPN-6174 > URL: https://issues.jboss.org/browse/ISPN-6174 > Project: Infinispan > Issue Type: Enhancement > Affects Versions: 8.2.0.Beta1 > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Minor > Fix For: 8.2.0.Beta2, 8.2.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-5367) Cache putMap/getAll usage of SegmentAwareMap/Set performance investigation

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-5367?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-5367: ---------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 8.2.0.Final Resolution: Done > Cache putMap/getAll usage of SegmentAwareMap/Set performance investigation > -------------------------------------------------------------------------- > > Key: ISPN-5367 > URL: https://issues.jboss.org/browse/ISPN-5367 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Reporter: William Burns > Assignee: William Burns > Fix For: 8.2.0.Beta2, 8.2.0.Final > > > With the putAll method I introduced a SegmentAwareMap and SegmentAwareSet in thoughts that not copying all the elements would help performance. Thinking more it may be better to just make a new shallow copy map for each target instead. Need to do some testing to make sure if one is clearly better than the other. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-6191) Provide Externalizers for (Double|Long|Int)SummaryStatistics

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6191?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6191: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Provide Externalizers for (Double|Long|Int)SummaryStatistics > ------------------------------------------------------------ > > Key: ISPN-6191 > URL: https://issues.jboss.org/browse/ISPN-6191 > Project: Infinispan > Issue Type: Enhancement > Reporter: William Burns > Assignee: William Burns > Fix For: 8.2.0.Beta2, 8.2.0.Final, 8.1.2.Final > > > The summary statistics classes are used directly by the new streams. Unfortunately they aren't Serializable by default, which can cause issues when using these methods in a distributed cache. > The summaryStatistics methods on the (Double|Long|Int)Stream use a hack of forcing an iterator to get these results, but this cannot be applied with the Collectors methods. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues February 2016