December 2018 - infinispan-issues

[JBoss JIRA] (ISPN-9631) REST API should return 503 Service Unavailable if store's becomes unavailable

by Galder Zamarreño (Jira)

[ https://issues.jboss.org/browse/ISPN-9631?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-9631: ----------------------------------- Fix Version/s: 10.0.0.Beta1 (was: 10.0.0.Alpha2) > REST API should return 503 Service Unavailable if store's becomes unavailable > ----------------------------------------------------------------------------- > > Key: ISPN-9631 > URL: https://issues.jboss.org/browse/ISPN-9631 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores, REST > Affects Versions: 9.4.0.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.0.Beta1 > > > The REST API should return a 503 if DB is down, or serve an in-memory value if X-Infinispan-Flags: SKIP_CACHE_STORE, SKIP_CACHE_LOAD are present. > AbstractOperations::createResponseException should be modified. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9801) ClusterTopologyManagerImpl hangs when restarting a node with FORK

by Galder Zamarreño (Jira)

[ https://issues.jboss.org/browse/ISPN-9801?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-9801: ----------------------------------- Fix Version/s: 10.0.0.Beta1 (was: 10.0.0.Alpha2) > ClusterTopologyManagerImpl hangs when restarting a node with FORK > ----------------------------------------------------------------- > > Key: ISPN-9801 > URL: https://issues.jboss.org/browse/ISPN-9801 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 10.0.0.Alpha1, 9.4.3.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 10.0.0.Beta1, 9.4.4.Final > > > When a server is restarted with `kill -9` or similar, both the old node and the new one can be in the JGroups view for a while. Normally this shouldn't be a problem, but sometimes the new node doesn't receive the {{HeartBeatCommand}} and the coordinator cannot process any new view updates. > {noformat} > 14:29:19,981 INFO (jgroups-12,Test-NodeA:[]) [CLUSTER] ISPN000094: Received new cluster view for channel FORKISPN: [Test-NodeA|4] (5) [Test-NodeA, Test-NodeB, Test-NodeC, Test-NodeD, Test-NodeE] > 14:29:19,982 TRACE (transport-thread-Test-NodeA-p4-t14:[ViewHandling]) [ClusterTopologyManagerImpl] Updating cluster members for all the caches. New list is [Test-NodeA, Test-NodeB, Test-NodeC, Test-NodeD, Test-NodeE] > 14:29:19,982 TRACE (transport-thread-Test-NodeA-p4-t14:[ViewHandling]) [JGroupsTransport] Test-NodeA sending request 9 to all: org.infinispan.topology.HeartBeatCommand@1163beb6 > 14:29:19,986 TRACE (jgroups-6,Test-NodeA:[]) [JGroupsTransport] Test-NodeA received response for request 9 from Test-NodeC: SuccessfulResponse(null) > 14:29:19,987 TRACE (jgroups-9,Test-NodeA:[]) [JGroupsTransport] Test-NodeA received response for request 9 from Test-NodeD: SuccessfulResponse(null) > 14:29:20,032 TRACE (jgroups-6,Test-NodeE:[]) [TCP_NIO2] Test-NodeE: received message batch of 1 messages from Test-NodeA > 14:29:20,032 TRACE (jgroups-6,Test-NodeE:[]) [NAKACK2] Test-NodeE: message Test-NodeA::39 was added to queue (not yet server) > 14:29:20,054 TRACE (jgroups-6,Test-NodeE:[]) [NAKACK2] Test-NodeE: received Test-NodeA#38 > 14:29:20,054 TRACE (jgroups-6,Test-NodeE:[]) [NAKACK2] Test-NodeE: delivering Test-NodeA#38 > # not actually delivered :) > 14:29:20,054 TRACE (jgroups-6,Test-NodeE:[]) [MFC] Test-NodeA used 5 credits, 1999995 remaining > 14:29:20,149 INFO (ForkThread-1,ForkChannelRestartTest:[]) [CLUSTER] ISPN000094: Received new cluster view for channel FORKISPN: [Test-NodeA|4] (5) [Test-NodeA, Test-NodeB, Test-NodeC, Test-NodeD, Test-NodeE] > 14:29:21,119 DEBUG (testng-Test-1:[]) [ForkChannelRestartTest] Stopping channel Test-NodeB > 14:29:23,319 INFO (VERIFY_SUSPECT.TimerThread-32,Test-NodeA:[]) [CLUSTER] ISPN000094: Received new cluster view for channel FORKISPN: [Test-NodeA|5] (4) [Test-NodeA, Test-NodeC, Test-NodeD, Test-NodeE] > 14:29:23,320 TRACE (remote-thread-Test-NodeA-p2-t1:[]) [MultiTargetRequest] Target Test-NodeB of request 9 left the cluster view > {noformat} > So far, it looks like it's a JGroups bug similar to JGRP-2294, but we need to investigate further. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9786) Update Prometheus JMX agent configuration pattern

by Galder Zamarreño (Jira)

[ https://issues.jboss.org/browse/ISPN-9786?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-9786: ----------------------------------- Fix Version/s: 10.0.0.Beta1 (was: 10.0.0.Alpha2) > Update Prometheus JMX agent configuration pattern > ------------------------------------------------- > > Key: ISPN-9786 > URL: https://issues.jboss.org/browse/ISPN-9786 > Project: Infinispan > Issue Type: Enhancement > Components: JMX, reporting and management > Affects Versions: 9.4.3.Final > Reporter: Vladimir Blagojevic > Assignee: Vladimir Blagojevic > Priority: Major > Fix For: 10.0.0.Beta1, 9.4.4.Final > > > The current JMX exporter pattern is not optimal. A better version that we should adopt is provided by Madou Coulibaly at https://github.com/mcouliba/datagrid-prometheus/blob/master/config.yaml -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9778) XidImpl implementations can optimize some byte[] allocations

by Galder Zamarreño (Jira)

[ https://issues.jboss.org/browse/ISPN-9778?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-9778: ----------------------------------- Fix Version/s: 10.0.0.Beta1 (was: 10.0.0.Alpha2) > XidImpl implementations can optimize some byte[] allocations > ------------------------------------------------------------ > > Key: ISPN-9778 > URL: https://issues.jboss.org/browse/ISPN-9778 > Project: Infinispan > Issue Type: Bug > Components: Transactions > Reporter: William Burns > Priority: Major > Fix For: 10.0.0.Beta1 > > > The EmbeddedXid and XidImpl classes show up on profiler for allocating byte[] in a local environment. > 1. We should be able to remove the branch byte[] completely as well as its accompanying AtomicInteger and just return an empty byte[] that is cached (ie. Util.EMPTY_BYTE_ARRAY). > 2. We can use the byte[] that is provided from the create method directly in XidImpl, which would reduce our allocation to just the 1 byte\[24\] for embedded or byte\[32\] for remote. > -3. We can return the byte[] directly for getGlobalTransactionId without copying.- -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9759) Hot Rod server non-hash aware topology updates can include non-members

by Galder Zamarreño (Jira)

[ https://issues.jboss.org/browse/ISPN-9759?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-9759: ----------------------------------- Fix Version/s: 10.0.0.Beta1 (was: 10.0.0.Alpha2) > Hot Rod server non-hash aware topology updates can include non-members > ---------------------------------------------------------------------- > > Key: ISPN-9759 > URL: https://issues.jboss.org/browse/ISPN-9759 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Server > Affects Versions: 9.4.2.Final > Reporter: Dan Berindei > Priority: Critical > Labels: testsuite_stability > Fix For: 10.0.0.Beta1 > > Attachments: HotRod12ReplicationTest.log.gz > > > When sending a non-hash aware topology update, the server includes all the servers that are present in the topology cache. This includes both servers that don't have the cache running yet (if the cache was started dynamically) and servers that are shutting down or already shutdown (because a node doesn't remove itself from the address cache before shutting down). > When a node shut down, the remaining nodes eventually see the view change and remove the stopped server from the address cache, but likely after sending a topology update with the new topology id to the clients. In cases where a rebalance is not necessary (e.g. replicated caches, or a single node is alive), a corrected topology update is never sent to the client. > This is causing random failures in {{HotRod10ReplicationTest.testReplicatedPutWithTopologyChanges}},{{HotRodReplicationTest.testReplicatedPutWithTopologyChanges}} and {{HotRod12ReplicationTest.testReplicatedPutWithTopologyChanges}} > I saw it on a pull request build first, but I see it (and its subclasses) has been randomly failing in master as well. I am able to reliably reproduce the failure on my machine if I add a small delay in {{CrashedMemberDetectorListener.detectCrashedMember()}}. > {noformat} > 16:24:18,288 ERROR (testng-Test:[]) [TestSuiteProgress] Test failed: org.infinispan.server.hotrod.HotRod12ReplicationTest.testReplicatedPutWithTopologyChanges > java.lang.AssertionError: expected:<3> but was:<2> > at org.testng.AssertJUnit.fail(AssertJUnit.java:59) ~[testng-6.9.9.jar:?] > at org.testng.AssertJUnit.failNotEquals(AssertJUnit.java:364) ~[testng-6.9.9.jar:?] > at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:80) ~[testng-6.9.9.jar:?] > at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:245) ~[testng-6.9.9.jar:?] > at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:252) ~[testng-6.9.9.jar:?] > at org.infinispan.server.hotrod.HotRodReplicationTest.testReplicatedPutWithTopologyChanges(HotRodReplicationTest.java:145) ~[test-classes/:?] > {noformat} > https://ci.infinispan.org/job/Infinispan/job/master/878/ -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9745) Release fails because compatibility bundle modules don't have source jars

by Galder Zamarreño (Jira)

[ https://issues.jboss.org/browse/ISPN-9745?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-9745: ----------------------------------- Fix Version/s: 10.0.0.Beta1 (was: 10.0.0.Alpha2) > Release fails because compatibility bundle modules don't have source jars > ------------------------------------------------------------------------- > > Key: ISPN-9745 > URL: https://issues.jboss.org/browse/ISPN-9745 > Project: Infinispan > Issue Type: Bug > Components: Build > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 10.0.0.Beta1, 9.4.4.Final > > > Modules {{client/marshaller/protostuff/protostuff-marshaller-compatibility-bundle}} and {{client/marshaller/protostuff/protostuff-marshaller-compatibility-bundle}} are uber-jars and don't have any sources. > Prior to the ISPN-9697 changes, a {{DEPENDENCIES.txt}} and {{LICENSES.txt}} was generated in the source directory, and a test-sources jar was created. But after those files were removed, a test-sources jar is no longer generated, and Nexus rejects the artifacts: > {noformat} > 11:19:37.492 [ERROR] > 11:19:37.492 [ERROR] Nexus Staging Rules Failure Report > 11:19:37.492 [ERROR] ================================== > 11:19:37.492 [ERROR] > 11:19:37.493 [ERROR] Repository "jboss_releases_staging_profile-14551" failures > 11:19:37.493 [ERROR] Rule "sources-staging" failures > 11:19:37.493 [ERROR] * Missing: no sources jar found in folder '/org/infinispan/infinispan-marshaller-kryo-bundle/9.4.2.Final' > 11:19:37.493 [ERROR] * Missing: no sources jar found in folder '/org/infinispan/infinispan-marshaller-protostuff-bundle/9.4.2.Final' > {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9726) Document max clause property on boolean query

by Galder Zamarreño (Jira)

[ https://issues.jboss.org/browse/ISPN-9726?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-9726: ----------------------------------- Fix Version/s: 10.0.0.Beta1 (was: 10.0.0.Alpha2) > Document max clause property on boolean query > --------------------------------------------- > > Key: ISPN-9726 > URL: https://issues.jboss.org/browse/ISPN-9726 > Project: Infinispan > Issue Type: Task > Components: Embedded Querying, Remote Querying > Affects Versions: 10.0.0.Alpha1 > Reporter: Katia Aresti > Assignee: Adrian Nistor > Priority: Major > Fix For: 10.0.0.Beta1, 9.4.4.Final > > > Document the ability to override org.apache.lucene.search.BooleanQuery.maxClauseCount using infinispan.query.lucene.max-boolean-clauses JVM system property. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9714) Update CacheNotifier to return CompletionStage

by Galder Zamarreño (Jira)

[ https://issues.jboss.org/browse/ISPN-9714?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-9714: ----------------------------------- Fix Version/s: 10.0.0.Beta1 (was: 10.0.0.Alpha2) > Update CacheNotifier to return CompletionStage > ---------------------------------------------- > > Key: ISPN-9714 > URL: https://issues.jboss.org/browse/ISPN-9714 > Project: Infinispan > Issue Type: Sub-task > Components: Core, Listeners > Reporter: William Burns > Assignee: William Burns > Priority: Major > Fix For: 10.0.0.Beta1 > > > We need to update CacheNotifier to return CompletionStage for all its appropriate methods. We also need to update all the internals to use these appropriately. > Not all notification usages may provide support non blocking, but our listener internals should support non blocking listeners for all. > The simplest way internally is to treat all current listeners as "alien" and invoke them in the notification thread pool. If it is sync we would wait for this task to complete. We would also now allow a listener to return a CompletionStage. If this is returned we will use this operate in a non blocking way. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9703) CI should test that distribution build works

by Galder Zamarreño (Jira)

[ https://issues.jboss.org/browse/ISPN-9703?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-9703: ----------------------------------- Fix Version/s: 10.0.0.Beta1 (was: 10.0.0.Alpha2) > CI should test that distribution build works > -------------------------------------------- > > Key: ISPN-9703 > URL: https://issues.jboss.org/browse/ISPN-9703 > Project: Infinispan > Issue Type: Enhancement > Affects Versions: 9.4.1.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.0.Beta1 > > > Currently the CI does not test whether the `-Pdistribution` profile successfully builds or not. As we want master to always be releasable, we should test this on PRs. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7035) Support Spring 5

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-7035?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-7035: ------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.4.4.Final Resolution: Done > Support Spring 5 > ---------------- > > Key: ISPN-7035 > URL: https://issues.jboss.org/browse/ISPN-7035 > Project: Infinispan > Issue Type: Enhancement > Reporter: Sebastian Łaskawiec > Assignee: Katia Aresti > Priority: Critical > Fix For: 10.0.0.Alpha2, 10.0.0.Final, 9.4.4.Final > > > Currently everything is placed in {{org.infinispan.spring}} package. We should provide exactly the same split as we did in CDI ({{org.infinispan.spring}} into {{org.infinispan.spring.remote}} and {{org.infinispan.spring.embedded}}) > Move to Spring 5.1.x.RELEASE, Spring Session 2.x and Spring-Boot 2.x -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues December 2018