January 2020 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-11185) Infinispan should not auto-export 'base' and 'vendor' MicroProfile metric registries

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/ISPN-11185?page=com.atlassian.jira.plugi... ] Paul Ferraro updated ISPN-11185: -------------------------------- Description: ISPN-11106 seems to assume that Infinispan is the only component using MicroProfile metrics. However, ultimately, the task of exporting base and vendor metrics is the responsibility of the MicroProfile container - not of an individual component. At the very least, I need to be able to disable the logic in ApplicationMetricsRegistry.start(). was: ISPN-11106 seems to assume that Infinispan is the only component using smallrye-metrics. Ultimately, the task of exporting base and vendor metrics is the responsibility of the MicroProfile container - not of an individual component. At the very least, I need to be able to disable this logic. > Infinispan should not auto-export 'base' and 'vendor' MicroProfile metric registries > ------------------------------------------------------------------------------------ > > Key: ISPN-11185 > URL: https://issues.redhat.com/browse/ISPN-11185 > Project: Infinispan > Issue Type: Bug > Components: Analytics > Affects Versions: 10.0.1.Final, 10.1.0.Final > Reporter: Paul Ferraro > Assignee: Nistor Adrian > Priority: Major > > ISPN-11106 seems to assume that Infinispan is the only component using MicroProfile metrics. > However, ultimately, the task of exporting base and vendor metrics is the responsibility of the MicroProfile container - not of an individual component. > At the very least, I need to be able to disable the logic in ApplicationMetricsRegistry.start(). -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11185) Infinispan should not auto-export 'base' and 'vendor' MicroProfile metric registries

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/ISPN-11185?page=com.atlassian.jira.plugi... ] Paul Ferraro updated ISPN-11185: -------------------------------- Description: ISPN-11106 seems to assume that Infinispan is the only component using smallrye-metrics. Ultimately, the task of exporting base and vendor metrics is the responsibility of the MicroProfile container - not of an individual component. At the very least, I need to be able to disable this logic. was: ISPN-11106 seems to assume that Infinispan is the only component using MicroProfile metrics. However, ultimately, the task of exporting base and vendor metrics is the responsibility of the MicroProfile container - not of an individual component. At the very least, I need to be able to disable this logic. > Infinispan should not auto-export 'base' and 'vendor' MicroProfile metric registries > ------------------------------------------------------------------------------------ > > Key: ISPN-11185 > URL: https://issues.redhat.com/browse/ISPN-11185 > Project: Infinispan > Issue Type: Bug > Components: Analytics > Affects Versions: 10.0.1.Final, 10.1.0.Final > Reporter: Paul Ferraro > Assignee: Nistor Adrian > Priority: Major > > ISPN-11106 seems to assume that Infinispan is the only component using smallrye-metrics. > Ultimately, the task of exporting base and vendor metrics is the responsibility of the MicroProfile container - not of an individual component. > At the very least, I need to be able to disable this logic. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11193) SocketTimeoutFailureRetryTest random failures

by Diego Lovison (Jira)

Diego Lovison created ISPN-11193: ------------------------------------ Summary: SocketTimeoutFailureRetryTest random failures Key: ISPN-11193 URL: https://issues.redhat.com/browse/ISPN-11193 Project: Infinispan Issue Type: Bug Components: Server, Test Suite Affects Versions: 10.1.0.Final Reporter: Diego Lovison Assignee: Dan Berindei Fix For: 11.0.0.Final Replicated non-tx caches without stores have an optimization for get operations to bypass the interceptor chain and query the data container directly. The optimization was added with the non-blocking listener changes, in order to compensate their overhead, but it only covered {{get()}} and {{getAsync()}}, while the HotRod server uses {{getCacheEntryAsync()}}. The ISPN-11020 fix extended the replicated get optimization to {{getCacheEntryAsync()}}, so now HotRod replicated reads bypass the interceptor chain, including the {{DelayingInterceptor}} added by {{SocketTimeoutFailureRetryTest}}. {noformat} java.lang.AssertionError: expected:<1> but was:<0> at org.testng.AssertJUnit.fail(AssertJUnit.java:59) at org.testng.AssertJUnit.failNotEquals(AssertJUnit.java:364) at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:80) at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:170) at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:177) at org.infinispan.client.hotrod.retry.SocketTimeoutFailureRetryTest.testRetrySocketTimeout(SocketTimeoutFailureRetryTest.java:68) {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10599) Jenkins pipeline for build and release operator

by Vittorio Rigamonti (Jira)

[ https://issues.redhat.com/browse/ISPN-10599?page=com.atlassian.jira.plugi... ] Vittorio Rigamonti updated ISPN-10599: -------------------------------------- Sprint: DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38 (was: DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38, DataGrid Sprint #39) > Jenkins pipeline for build and release operator > ----------------------------------------------- > > Key: ISPN-10599 > URL: https://issues.redhat.com/browse/ISPN-10599 > Project: Infinispan > Issue Type: Feature Request > Components: Operator > Reporter: Vittorio Rigamonti > Assignee: Vittorio Rigamonti > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10599) Jenkins pipeline for build and release operator

by Vittorio Rigamonti (Jira)

[ https://issues.redhat.com/browse/ISPN-10599?page=com.atlassian.jira.plugi... ] Vittorio Rigamonti closed ISPN-10599. ------------------------------------- Resolution: Done > Jenkins pipeline for build and release operator > ----------------------------------------------- > > Key: ISPN-10599 > URL: https://issues.redhat.com/browse/ISPN-10599 > Project: Infinispan > Issue Type: Feature Request > Components: Operator > Reporter: Vittorio Rigamonti > Assignee: Vittorio Rigamonti > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10113) Cluster description properties should be under `spec` field

by Vittorio Rigamonti (Jira)

[ https://issues.redhat.com/browse/ISPN-10113?page=com.atlassian.jira.plugi... ] Vittorio Rigamonti closed ISPN-10113. ------------------------------------- Resolution: Out of Date > Cluster description properties should be under `spec` field > ----------------------------------------------------------- > > Key: ISPN-10113 > URL: https://issues.redhat.com/browse/ISPN-10113 > Project: Infinispan > Issue Type: Feature Request > Components: Operator > Reporter: Vittorio Rigamonti > Assignee: Vittorio Rigamonti > Priority: Major > > As specified in [k8s doc|https://github.com/kubernetes/community/blob/master/contributors/deve...] desired status of an object must be under `spec` field. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10053) Enable authenticated cache access

by Vittorio Rigamonti (Jira)

[ https://issues.redhat.com/browse/ISPN-10053?page=com.atlassian.jira.plugi... ] Vittorio Rigamonti updated ISPN-10053: -------------------------------------- Status: Open (was: Pull Request Sent) this is an obsolete PR not merged > Enable authenticated cache access > --------------------------------- > > Key: ISPN-10053 > URL: https://issues.redhat.com/browse/ISPN-10053 > Project: Infinispan > Issue Type: Feature Request > Components: Operator > Reporter: Vittorio Rigamonti > Assignee: Vittorio Rigamonti > Priority: Major > > Operator must allow the user to configure authenticated access to the cache with user, password and role. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10053) Enable authenticated cache access

by Vittorio Rigamonti (Jira)

[ https://issues.redhat.com/browse/ISPN-10053?page=com.atlassian.jira.plugi... ] Vittorio Rigamonti closed ISPN-10053. ------------------------------------- Resolution: Out of Date > Enable authenticated cache access > --------------------------------- > > Key: ISPN-10053 > URL: https://issues.redhat.com/browse/ISPN-10053 > Project: Infinispan > Issue Type: Feature Request > Components: Operator > Reporter: Vittorio Rigamonti > Assignee: Vittorio Rigamonti > Priority: Major > > Operator must allow the user to configure authenticated access to the cache with user, password and role. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11192) EvictInvalidatedNearCacheTest.testEvictAfterReachingMax random failures

by Diego Lovison (Jira)

Diego Lovison created ISPN-11192: ------------------------------------ Summary: EvictInvalidatedNearCacheTest.testEvictAfterReachingMax random failures Key: ISPN-11192 URL: https://issues.redhat.com/browse/ISPN-11192 Project: Infinispan Issue Type: Bug Components: Test Suite Affects Versions: 10.0.0.Beta3 Reporter: Diego Lovison Assignee: Will Burns Fix For: 10.0.0.Beta4 >From the log, it looks like the near cache may ignore put requests, and {{EvictInvalidatedNearCacheTest}} doesn't expect that: {noformat} 22:02:29,709 TRACE (testng-Test:[]) [RetryOnFailureOperation] About to start executing operation GetWithMetadataOperation{(default), key=[B0x034B00000002, flags=0} on [id: 0x2ca8c2fb, L:/127.0.0.1:40582 - R:127.0.0.1/127.0.0.1:33741] 22:02:29,709 TRACE (testng-Test:[]) [Codec] [] Wrote header for messageId=5085 to PooledUnsafeDirectByteBuf(ridx: 0, widx: 13, cap: 21). Operation code: 0x1b(UNKNOWN). Flags: 0x0. Topology id: -1 22:02:29,710 TRACE (Test-Client-Async-108-1:[]) [HeaderDecoder] Response 5085 belongs to GetWithMetadataOperation{(default), key=[B0x034B00000002, flags=0} on [id: 0x2ca8c2fb, L:/127.0.0.1:40582 - R:127.0.0.1/127.0.0.1:33741] 22:02:29,710 TRACE (Test-Client-Async-108-1:[]) [NearCacheService] Conditionally put key=2 and value=MetadataValueImpl [created=-1, lifespan=-1, lastUsed=-1, maxIdle=-1, getVersion()=2, getValue()=v1] if absent in near cache (listenerId=[B0xD532F51E0F6632E1..[16]) 22:02:29,725 ERROR (testng-Test:[]) [TestSuiteProgress] Test failed: org.infinispan.client.hotrod.near.EvictInvalidatedNearCacheTest.testEvictAfterReachingMax java.lang.AssertionError: expected:<v1> but was:<null> 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:88) ~[testng-6.14.3.jar:?] at org.infinispan.client.hotrod.near.AssertsNearCache.assertGetKeyValue(AssertsNearCache.java:235) ~[test-classes/:?] at org.infinispan.client.hotrod.near.AssertsNearCache.expectNearGetValue(AssertsNearCache.java:130) ~[test-classes/:?] at org.infinispan.client.hotrod.near.EvictInvalidatedNearCacheTest.testEvictAfterReachingMax(EvictInvalidatedNearCacheTest.java:39) ~[test-classes/:?] {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9498) Index filesystem paths in server should point to data directory

by Pedro Zapata Fernandez (Jira)

[ https://issues.redhat.com/browse/ISPN-9498?page=com.atlassian.jira.plugin... ] Pedro Zapata Fernandez updated ISPN-9498: ----------------------------------------- Sprint: Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 9.4.0.Final, Sprint 10.0.0.Alpha0, Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38 (was: Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 9.4.0.Final, Sprint 10.0.0.Alpha0, Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38, DataGrid Sprint #39) > Index filesystem paths in server should point to data directory > --------------------------------------------------------------- > > Key: ISPN-9498 > URL: https://issues.redhat.com/browse/ISPN-9498 > Project: Infinispan > Issue Type: Bug > Components: Indexing, OpenShift, Server > Affects Versions: 9.4.0.CR1, 9.3.3.Final > Reporter: Galder Zamarreño > Assignee: Tristan Tarrant > Priority: Major > > Certain indexing configurations result in using filesystem as index storage. > When running such configurations in a server environment, filesystem path should be somewhere within the server's data directory. This is the natural place for such data. > When running in OpenShift, server's data folder can be backed by a persistent volume. This means that the fileystem volume survives after restarts. > Plugging server's data directory is already happening for [file-store|https://github.com/infinispan/infinispan/blob/master/server/in...] and [rocksdb-store|https://github.com/infinispan/infinispan/blob/master/server...]. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 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 January 2020