May 2018 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-9145) DistributedStreamTest.testIntSortedLimit random failure

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-9145?page=com.atlassian.jira.plugin.... ] William Burns reassigned ISPN-9145: ----------------------------------- Assignee: William Burns > DistributedStreamTest.testIntSortedLimit random failure > ------------------------------------------------------- > > Key: ISPN-9145 > URL: https://issues.jboss.org/browse/ISPN-9145 > Project: Infinispan > Issue Type: Bug > Components: Streams, Test Suite - Core > Reporter: William Burns > Assignee: William Burns > > There was a random failure on this PR https://ci.infinispan.org/job/Infinispan/job/PR-5794/23/ > {quote} > testIntSortedLimit[DIST_SYNC, tx=false] > java.lang.AssertionError: expected:<0> but was:<2> at org.infinispan.stream.BaseStreamTest.testIntSortedLimit(BaseStreamTest.java:1157) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) ... Removed 21 stack frames > {quote} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9144) Document AdvancedCacheLoader semantics

by William Burns (JIRA)

William Burns created ISPN-9144: ----------------------------------- Summary: Document AdvancedCacheLoader semantics Key: ISPN-9144 URL: https://issues.jboss.org/browse/ISPN-9144 Project: Infinispan Issue Type: Task Components: Loaders and Stores Reporter: William Burns Unfortunately the behavior of how are stores operate is not very transparent to the user. For example you can configure multiple stores/loaders. However it is not clear how this works with bulk operations, such as size or iterator. This was discussed in https://github.com/infinispan/infinispan/pull/5794#discussion_r173854664 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9144) Document AdvancedCacheLoader semantics

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-9144?page=com.atlassian.jira.plugin.... ] William Burns reassigned ISPN-9144: ----------------------------------- Assignee: William Burns > Document AdvancedCacheLoader semantics > -------------------------------------- > > Key: ISPN-9144 > URL: https://issues.jboss.org/browse/ISPN-9144 > Project: Infinispan > Issue Type: Task > Components: Loaders and Stores > Reporter: William Burns > Assignee: William Burns > > Unfortunately the behavior of how are stores operate is not very transparent to the user. For example you can configure multiple stores/loaders. However it is not clear how this works with bulk operations, such as size or iterator. > This was discussed in https://github.com/infinispan/infinispan/pull/5794#discussion_r173854664 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9143) Some stores may not allow expired entries

by William Burns (JIRA)

William Burns created ISPN-9143: ----------------------------------- Summary: Some stores may not allow expired entries Key: ISPN-9143 URL: https://issues.jboss.org/browse/ISPN-9143 Project: Infinispan Issue Type: Task Components: Loaders and Stores Reporter: William Burns Assignee: William Burns JpaStore currently can be configured to not store metadata. This prevents this store from ever expiring the given entry. This can be an issue when the user expected an entry to be removed. We need to somehow notify the user of this occurring. Further discussion about this can be found at https://github.com/infinispan/infinispan/pull/5794#discussion_r187357514 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8865) Move AdvancedCacheLoader over to using Publisher instead of process

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-8865?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-8865: ------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.3.0.Beta1 Resolution: Done > Move AdvancedCacheLoader over to using Publisher instead of process > ------------------------------------------------------------------- > > Key: ISPN-8865 > URL: https://issues.jboss.org/browse/ISPN-8865 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores > Reporter: William Burns > Assignee: William Burns > Fix For: 9.3.0.Beta1, 9.3.0.Final > > > Currently our process method on AdvancedCacheLoader is very hard to write for proper thread usage, see [1]. There is no way to utilize the main thread to help with processing as well, except by always using a WithinThreadExecutor, which prevents any parallelism. > Instead we should have the loader expose a Producer which can be properly controlled and have backpressure built in (thus not wasting threads or resources like it does currently. > [1] https://github.com/infinispan/infinispan/blob/master/core/src/main/java/o... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8865) Move AdvancedCacheLoader over to using Publisher instead of process

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-8865?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-8865: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/5794 > Move AdvancedCacheLoader over to using Publisher instead of process > ------------------------------------------------------------------- > > Key: ISPN-8865 > URL: https://issues.jboss.org/browse/ISPN-8865 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores > Reporter: William Burns > Assignee: William Burns > Fix For: 9.3.0.Beta1, 9.3.0.Final > > > Currently our process method on AdvancedCacheLoader is very hard to write for proper thread usage, see [1]. There is no way to utilize the main thread to help with processing as well, except by always using a WithinThreadExecutor, which prevents any parallelism. > Instead we should have the loader expose a Producer which can be properly controlled and have backpressure built in (thus not wasting threads or resources like it does currently. > [1] https://github.com/infinispan/infinispan/blob/master/core/src/main/java/o... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8865) Move AdvancedCacheLoader over to using Publisher instead of process

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-8865?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-8865: ------------------------------- Status: Open (was: New) > Move AdvancedCacheLoader over to using Publisher instead of process > ------------------------------------------------------------------- > > Key: ISPN-8865 > URL: https://issues.jboss.org/browse/ISPN-8865 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores > Reporter: William Burns > Assignee: William Burns > Fix For: 9.3.0.Beta1, 9.3.0.Final > > > Currently our process method on AdvancedCacheLoader is very hard to write for proper thread usage, see [1]. There is no way to utilize the main thread to help with processing as well, except by always using a WithinThreadExecutor, which prevents any parallelism. > Instead we should have the loader expose a Producer which can be properly controlled and have backpressure built in (thus not wasting threads or resources like it does currently. > [1] https://github.com/infinispan/infinispan/blob/master/core/src/main/java/o... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (HRJS-60) Client does not have a reconnection attempts mechanism when hotrod servers fall

by Rafa Eska (JIRA)

Rafa Eska created HRJS-60: ----------------------------- Summary: Client does not have a reconnection attempts mechanism when hotrod servers fall Key: HRJS-60 URL: https://issues.jboss.org/browse/HRJS-60 Project: Infinispan Javascript client Issue Type: Feature Request Affects Versions: 0.4.0, 0.5.0 Environment: All. Running Node 8.6.0 Reporter: Rafa Eska Client does not reconnect to a cluster that has been down -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (HRJS-59) Under heavy load of servers and javascript client ERROR messages about timeouts can starve resources in limited environments (kubernetes/openshift)

by Rafa Eska (JIRA)

Rafa Eska created HRJS-59: ----------------------------- Summary: Under heavy load of servers and javascript client ERROR messages about timeouts can starve resources in limited environments (kubernetes/openshift) Key: HRJS-59 URL: https://issues.jboss.org/browse/HRJS-59 Project: Infinispan Javascript client Issue Type: Enhancement Affects Versions: 0.4.0 Environment: Node 8.6.0 in a container inside Openshift with limits of 1000 millicores and 1000MB of memory Infinispan 'Chakra' 8.4.0.Final-redhat-3 running in 2 pods running image registry.access.redhat.com/jboss-datagrid-7/datagrid71-openshift/images/1... with limits of 1000 millicores and 1000MB of memory Reporter: Rafa Eska During charge tests Infinispan undersizes server end denegating service, and Javascript Hotrod client consume all Node.js pod resources emitting this:{{ {code:java} [31m[2018-05-10 12:38:24.956] [ERROR] decoder - [39mError decoding body of request(msgId=366322): org.infinispan.util.concurrent.TimeoutException: Timed out waiting for responses [31m[2018-05-10 12:38:24.957] [ERROR] decoder - [39mError decoding body of request(msgId=366322): org.infinispan.util.concurrent.TimeoutException: Timed out waiting for responses [31m[2018-05-10 12:38:24.957] [ERROR] decoder -[39mError decoding body of request(msgId=366322): org.infinispan.util.concurrent.TimeoutException: Timed out waiting for responses jdg error org.infinispan.util.concurrent.TimeoutException: Timed out waiting for responses [31m[2018-05-10 12:38:24.958] [ERROR] decoder -[39mError decoding body of request(msgId=366322): org.infinispan.util.concurrent.TimeoutException: Timed out waiting for responses [31m[2018-05-10 12:38:24.958] [ERROR] io_1_conn_5 - [39mError received but rpc not found for (msgId=366322) [31m[2018-05-10 12:38:24.958] [ERROR] decoder - [39mError decoding body of request(msgId=366322): org.infinispan.util.concurrent.TimeoutException: Timed out waiting for responses [31m[2018-05-10 12:38:24.958] [ERROR] io_1_conn_5 - [39mError received but rpc not found for (msgId=366322) [31m[2018-05-10 12:38:24.958] [ERROR] decoder - [39mError decoding body of request(msgId=366322): org.infinispan.util.concurrent.TimeoutException: Timed out waiting for responses [31m[2018-05-10 12:38:24.958] [ERROR] io_1_conn_5 - [39mError received but rpc not found for (msgId=366322) {code} }} Shouldn't it be WARNINGS? Or control in any way number of emitted messages? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9142) PreferConsistencyStrategy does not initiate CR when previously independent nodes merge

by Ryan Emerson (JIRA)

Ryan Emerson created ISPN-9142: ---------------------------------- Summary: PreferConsistencyStrategy does not initiate CR when previously independent nodes merge Key: ISPN-9142 URL: https://issues.jboss.org/browse/ISPN-9142 Project: Infinispan Issue Type: Bug Components: Core Affects Versions: 9.3.0.Alpha1 Reporter: Ryan Emerson Assignee: Ryan Emerson Fix For: 9.3.0.Final Two nodes start operating independently and don't know about each other due to a network issue. Both nodes put one record with same key but different value. When the network recovers, CR is not initiated. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 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 May 2018