December 2019 - infinispan-issues

[JBoss JIRA] (ISPN-11082) Remove preferContainerExposedPorts from Jenkinsfile

by Diego Lovison (Jira)

Diego Lovison created ISPN-11082: ------------------------------------ Summary: Remove preferContainerExposedPorts from Jenkinsfile Key: ISPN-11082 URL: https://issues.redhat.com/browse/ISPN-11082 Project: Infinispan Issue Type: Bug Reporter: Diego Lovison preferContainerExposedPorts is only required when running on MAC -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10830) Client Testsuite should utilise SerializationContextInitializers via normal configuration

by Ryan Emerson (Jira)

[ https://issues.redhat.com/browse/ISPN-10830?page=com.atlassian.jira.plugi... ] Work on ISPN-10830 started by Ryan Emerson. ------------------------------------------- > Client Testsuite should utilise SerializationContextInitializers via normal configuration > ----------------------------------------------------------------------------------------- > > Key: ISPN-10830 > URL: https://issues.redhat.com/browse/ISPN-10830 > Project: Infinispan > Issue Type: Enhancement > Components: Test Suite > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > > The client testsuite makes extensive use of the {{ProtobufMetadataManagerImpl::registerMarshaller}} method to register ProtoStream marshallers, however this is no longer necessary as we now expose the SerializationContextInitializer via our server configuration. > Furthermore, it's also possible to directly use SerializationContextInitializer instances via the client configuration. > The client testsuite should be updated to utilise ^ mechanisms. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10830) Client Testsuite should utilise SerializationContextInitializers via normal configuration

by Ryan Emerson (Jira)

[ https://issues.redhat.com/browse/ISPN-10830?page=com.atlassian.jira.plugi... ] Ryan Emerson updated ISPN-10830: -------------------------------- Status: Open (was: New) > Client Testsuite should utilise SerializationContextInitializers via normal configuration > ----------------------------------------------------------------------------------------- > > Key: ISPN-10830 > URL: https://issues.redhat.com/browse/ISPN-10830 > Project: Infinispan > Issue Type: Enhancement > Components: Test Suite > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > > The client testsuite makes extensive use of the {{ProtobufMetadataManagerImpl::registerMarshaller}} method to register ProtoStream marshallers, however this is no longer necessary as we now expose the SerializationContextInitializer via our server configuration. > Furthermore, it's also possible to directly use SerializationContextInitializer instances via the client configuration. > The client testsuite should be updated to utilise ^ mechanisms. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11058) Upgrade to JGroups 4.1.8.Final

by Katia Aresti (Jira)

[ https://issues.redhat.com/browse/ISPN-11058?page=com.atlassian.jira.plugi... ] Katia Aresti updated ISPN-11058: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Upgrade to JGroups 4.1.8.Final > ------------------------------ > > Key: ISPN-11058 > URL: https://issues.redhat.com/browse/ISPN-11058 > Project: Infinispan > Issue Type: Component Upgrade > Components: Dependency > Affects Versions: 10.1.0.CR1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 10.1.0.Final > > > JGroups 4.1.8.Final includes fixes for two LOCAL_PING issues that affect our test suite: > * JGRP-2395 LOCAL_PING fails when 2 nodes start at the same time > * JGRP-2398 LOCAL_PING should remove local PingData on stop > The upgrade will allow us to remove the workaround for JGRP-2398 ({{GMS.num_join_attempts="1"}}), which is causing random failures in {{InitialClusterSizeTest}}. > {noformat} > java.util.concurrent.ExecutionException: org.infinispan.manager.EmbeddedCacheManagerStartupException: > org.infinispan.util.concurrent.TimeoutException: ISPN000399: Timeout while waiting for 4 members in cluster. Last view had [InitialClusterSizeTest-NodeD-26330, InitialClusterSizeTest-NodeC-48323] > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10999) Server Docs: Update prometheus monitoring section

by Donald Naro (Jira)

[ https://issues.redhat.com/browse/ISPN-10999?page=com.atlassian.jira.plugi... ] Donald Naro updated ISPN-10999: ------------------------------- Description: Document ./standalone.sh -c cloud.xml --jmx 8180:my-config.yaml to override prometheus_config.yaml (was: Need to make some changes to include the server README.adoc file in product docs.) > Server Docs: Update prometheus monitoring section > ------------------------------------------------- > > Key: ISPN-10999 > URL: https://issues.redhat.com/browse/ISPN-10999 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Minor > Fix For: 10.1.0.CR1 > > > Document ./standalone.sh -c cloud.xml --jmx 8180:my-config.yaml to override prometheus_config.yaml -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10999) Server Docs: Update prometheus monitoring section

by Donald Naro (Jira)

[ https://issues.redhat.com/browse/ISPN-10999?page=com.atlassian.jira.plugi... ] Donald Naro updated ISPN-10999: ------------------------------- Status: Pull Request Sent (was: Reopened) Git Pull Request: https://github.com/infinispan/infinispan/pull/7626, https://github.com/infinispan/infinispan/pull/7625, https://github.com/infinispan/infinispan/pull/7682 (was: https://github.com/infinispan/infinispan/pull/7626, https://github.com/infinispan/infinispan/pull/7625) > Server Docs: Update prometheus monitoring section > ------------------------------------------------- > > Key: ISPN-10999 > URL: https://issues.redhat.com/browse/ISPN-10999 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Minor > Fix For: 10.1.0.CR1 > > > Need to make some changes to include the server README.adoc file in product docs. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10999) Server Docs: Update prometheus monitoring section

by Donald Naro (Jira)

[ https://issues.redhat.com/browse/ISPN-10999?page=com.atlassian.jira.plugi... ] Donald Naro reopened ISPN-10999: -------------------------------- Reopening to fix 9.4.x/7.3.x > Server Docs: Update prometheus monitoring section > ------------------------------------------------- > > Key: ISPN-10999 > URL: https://issues.redhat.com/browse/ISPN-10999 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Minor > Fix For: 10.1.0.CR1 > > > Need to make some changes to include the server README.adoc file in product docs. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10999) Server Docs: Update prometheus monitoring section

by Donald Naro (Jira)

[ https://issues.redhat.com/browse/ISPN-10999?page=com.atlassian.jira.plugi... ] Donald Naro updated ISPN-10999: ------------------------------- Sprint: DataGrid Sprint #37, DataGrid Sprint #38 (was: DataGrid Sprint #37) > Server Docs: Update prometheus monitoring section > ------------------------------------------------- > > Key: ISPN-10999 > URL: https://issues.redhat.com/browse/ISPN-10999 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Minor > Fix For: 10.1.0.CR1 > > > Need to make some changes to include the server README.adoc file in product docs. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11077) TransactionsSpanningReplicatedCachesTest.testReadOnlyTransaction random failures

by Katia Aresti (Jira)

[ https://issues.redhat.com/browse/ISPN-11077?page=com.atlassian.jira.plugi... ] Katia Aresti updated ISPN-11077: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > TransactionsSpanningReplicatedCachesTest.testReadOnlyTransaction random failures > -------------------------------------------------------------------------------- > > Key: ISPN-11077 > URL: https://issues.redhat.com/browse/ISPN-11077 > Project: Infinispan > Issue Type: Bug > Components: Core, Test Suite > Affects Versions: 10.1.0.CR1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Labels: testsuite_stability > Fix For: 10.1.0.Final > > > I have only seen it once, with trace logging enabled. > Because the test doesn't wait for the rebalance to finish before starting the transaction, the transaction's topology might be smaller than the current topology, and {{TxDistributionInterceptor}} will send the prepare+commit to all the owners "just in case". > {noformat} > 00:55:24,535 TRACE (testng-Test:[]) [TransactionTable] Created a new local transaction: LocalXaTransaction{xid=null} LocalTransaction{remoteLockedNodes=null, isMarkedForRollback=false, lockedKeys=[], backupKeyLocks=[], topologyId=4, stateTransferFlag=null} org.infinispan.transaction.xa.LocalXaTransaction@23b3 > 00:55:24,539 TRACE (transport-thread-Test-NodeA-p22422-t4:[]) [CacheNotifierImpl] Invoking listener: org.infinispan.transaction.xa.XaTransactionTable@7d35d8bc passing event EventImpl{type=TOPOLOGY_CHANGED, pre=false, cache=Cache 'Test'@Test-NodeA-2639, readConsistentHashAtStart=PartitionerConsistentHash:ReplicatedConsistentHash{ns = 256, owners = (2)[Test-NodeA-2639: 128, Test-NodeB-29221: 128]}, writeConsistentHashAtStart=PartitionerConsistentHash:ReplicatedConsistentHash{ns = 256, owners = (2)[Test-NodeA-2639: 128, Test-NodeB-29221: 128]}, readConsistentHashAtEnd=PartitionerConsistentHash:ReplicatedConsistentHash{ns = 256, owners = (2)[Test-NodeA-2639: 128, Test-NodeB-29221: 128]}, writeConsistentHashAtEnd=PartitionerConsistentHash:ReplicatedConsistentHash{ns = 256, owners = (2)[Test-NodeA-2639: 128, Test-NodeB-29221: 128]}, unionConsistentHash=null, newTopologyId=5} > 00:55:24,540 TRACE (testng-Test:[]) [VersionedDistributionInterceptor] Should invoke remotely? true. hasModifications=false, hasRemoteLocksAcquired=false > 00:55:24,557 ERROR (testng-Test:[]) [TestSuiteProgress] Test failed: org.infinispan.tx.TransactionsSpanningReplicatedCachesTest.testReadOnlyTransaction > java.lang.AssertionError: expected:<6> but was:<4> > at org.testng.AssertJUnit.fail(AssertJUnit.java:59) ~[testng-6.14.3.jar:?] > at org.testng.AssertJUnit.failNotEquals(AssertJUnit.java:364) ~[testng-6.14.3.jar:?] > at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:80) ~[testng-6.14.3.jar:?] > at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:170) ~[testng-6.14.3.jar:?] > at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:177) ~[testng-6.14.3.jar:?] > at org.infinispan.tx.TransactionsSpanningReplicatedCachesTest.testReadOnlyTransaction(TransactionsSpanningReplicatedCachesTest.java:71) ~[test-classes/:?] > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11081) Data Store

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11081?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11081: ----------------------------------- Git Pull Request: https://github.com/infinispan/infinispan-designs/pull/15 > Data Store > ---------- > > Key: ISPN-11081 > URL: https://issues.redhat.com/browse/ISPN-11081 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 10.1.0.CR1 > Reporter: Tristan Tarrant > Assignee: Dan Berindei > Priority: Major > Fix For: 11.0.0.Final > > > In scenarios where Infinispan is used as a persistent data store, the elasticity provided by rebalancing on scaling down (either voluntarily or because of node failure) can lead to data loss, even with persistent caches if all the owners of a segment leave the cluster before rebalancing can be completed. The remaining cluster should prevent writes to the lost segments until the nodes that own them are restarted. > It should be possible to configure Infinispan so that elasticity only applies when scaling up, i.e. adding a node will cause a rebalance. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 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 2019