September 2017 - infinispan-issues

[JBoss JIRA] (ISPN-8339) Cache Stream response should send asynchronously

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-8339?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-8339: -------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/5461 > Cache Stream response should send asynchronously > ------------------------------------------------ > > Key: ISPN-8339 > URL: https://issues.jboss.org/browse/ISPN-8339 > Project: Infinispan > Issue Type: Bug > Components: Distributed Execution and Map/Reduce > Reporter: William Burns > Assignee: William Burns > Fix For: 9.2.0.Alpha1 > > > When a cache stream completes a request it sends that back to the requestor. Currently this is using RpcManager.invokeRemotely such as [1]. This is causing the remote nodes to use a remote thread to wait for the response to process. We should instead send this asynchronously so we don't have to keep the remote thread used. This can cause exhaustion if you have too many requests since these responses are also processed on the remote thread pool. > [1] https://github.com/infinispan/infinispan/blob/master/core/src/main/java/o... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8339) Cache Stream response should send asynchronously

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-8339?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-8339: -------------------------------- Status: Open (was: New) > Cache Stream response should send asynchronously > ------------------------------------------------ > > Key: ISPN-8339 > URL: https://issues.jboss.org/browse/ISPN-8339 > Project: Infinispan > Issue Type: Bug > Components: Distributed Execution and Map/Reduce > Reporter: William Burns > Fix For: 9.2.0.Alpha1 > > > When a cache stream completes a request it sends that back to the requestor. Currently this is using RpcManager.invokeRemotely such as [1]. This is causing the remote nodes to use a remote thread to wait for the response to process. We should instead send this asynchronously so we don't have to keep the remote thread used. This can cause exhaustion if you have too many requests since these responses are also processed on the remote thread pool. > [1] https://github.com/infinispan/infinispan/blob/master/core/src/main/java/o... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8339) Cache Stream response should send asynchronously

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-8339?page=com.atlassian.jira.plugin.... ] Work on ISPN-8339 started by William Burns. ------------------------------------------- > Cache Stream response should send asynchronously > ------------------------------------------------ > > Key: ISPN-8339 > URL: https://issues.jboss.org/browse/ISPN-8339 > Project: Infinispan > Issue Type: Bug > Components: Distributed Execution and Map/Reduce > Reporter: William Burns > Assignee: William Burns > Fix For: 9.2.0.Alpha1 > > > When a cache stream completes a request it sends that back to the requestor. Currently this is using RpcManager.invokeRemotely such as [1]. This is causing the remote nodes to use a remote thread to wait for the response to process. We should instead send this asynchronously so we don't have to keep the remote thread used. This can cause exhaustion if you have too many requests since these responses are also processed on the remote thread pool. > [1] https://github.com/infinispan/infinispan/blob/master/core/src/main/java/o... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8339) Cache Stream response should send asynchronously

by William Burns (JIRA)

William Burns created ISPN-8339: ----------------------------------- Summary: Cache Stream response should send asynchronously Key: ISPN-8339 URL: https://issues.jboss.org/browse/ISPN-8339 Project: Infinispan Issue Type: Bug Components: Distributed Execution and Map/Reduce Reporter: William Burns Fix For: 9.2.0.Alpha1 When a cache stream completes a request it sends that back to the requestor. Currently this is using RpcManager.invokeRemotely such as [1]. This is causing the remote nodes to use a remote thread to wait for the response to process. We should instead send this asynchronously so we don't have to keep the remote thread used. This can cause exhaustion if you have too many requests since these responses are also processed on the remote thread pool. [1] https://github.com/infinispan/infinispan/blob/master/core/src/main/java/o... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8338) Cache start methods should run privileged

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-8338?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-8338: -------------------------------- Status: Open (was: New) > Cache start methods should run privileged > ----------------------------------------- > > Key: ISPN-8338 > URL: https://issues.jboss.org/browse/ISPN-8338 > Project: Infinispan > Issue Type: Task > Components: Security > Reporter: William Burns > Assignee: William Burns > Fix For: 9.2.0.Alpha1 > > > When a cache is starting and it has security, it is possible that an internal component would throw an exception stating it doesn't have security access. Normally this is fixed by surrounding this in a SecurityActions call. However when a cache is starting all of these components are known to be Infinispan core and should be fine trusting it. This JIRA is to wrap start automatically with SecurityActions. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8338) Cache start methods should run privileged

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-8338?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-8338: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/5448 > Cache start methods should run privileged > ----------------------------------------- > > Key: ISPN-8338 > URL: https://issues.jboss.org/browse/ISPN-8338 > Project: Infinispan > Issue Type: Task > Components: Security > Reporter: William Burns > Assignee: William Burns > Fix For: 9.2.0.Alpha1 > > > When a cache is starting and it has security, it is possible that an internal component would throw an exception stating it doesn't have security access. Normally this is fixed by surrounding this in a SecurityActions call. However when a cache is starting all of these components are known to be Infinispan core and should be fine trusting it. This JIRA is to wrap start automatically with SecurityActions. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7865) Distributed Stream thread usage for key aware operations can be improved

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-7865?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-7865: -------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/5448 (was: https://github.com/infinispan/infinispan/pull/5283, https://github.com/infinispan/infinispan/pull/5314) > Distributed Stream thread usage for key aware operations can be improved > ------------------------------------------------------------------------ > > Key: ISPN-7865 > URL: https://issues.jboss.org/browse/ISPN-7865 > Project: Infinispan > Issue Type: Enhancement > Components: Core, Distributed Execution and Map/Reduce > Reporter: William Burns > Assignee: William Burns > Fix For: 9.2.0.Final > > > Currently iterator will block a thread on the remote server when it is trying to send back a response. It would be better if we used full async API to instead request blocks of values as the iterator consumes them. We should make sure we always maintain a distributed batch size worth. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8338) Cache start methods should run privileged

by William Burns (JIRA)

William Burns created ISPN-8338: ----------------------------------- Summary: Cache start methods should run privileged Key: ISPN-8338 URL: https://issues.jboss.org/browse/ISPN-8338 Project: Infinispan Issue Type: Task Components: Security Reporter: William Burns Assignee: William Burns Fix For: 9.2.0.Alpha1 When a cache is starting and it has security, it is possible that an internal component would throw an exception stating it doesn't have security access. Normally this is fixed by surrounding this in a SecurityActions call. However when a cache is starting all of these components are known to be Infinispan core and should be fine trusting it. This JIRA is to wrap start automatically with SecurityActions. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8337) Empty results from queries from QueryFactory with offheap

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-8337?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-8337: ------------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/5460 > Empty results from queries from QueryFactory with offheap > --------------------------------------------------------- > > Key: ISPN-8337 > URL: https://issues.jboss.org/browse/ISPN-8337 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Affects Versions: 9.1.1.Final > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Fix For: 9.1.2.Final, 9.2.0.Alpha1 > > > When enabling Storage.OFF_HEAP or Storage.BINARY, queries obtained from {{Search.getQueryFactory}} return empty results. Queries built > with Lucene from {{Search.getSearchManager}} are not affected. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8337) Empty results from queries from QueryFactory with offheap

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPN-8337?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes updated ISPN-8337: ------------------------------------ Description: When enabling Storage.OFF_HEAP or Storage.BINARY, queries obtained from {{Search.getQueryFactory}} return empty results. Queries build with Lucene from {{Search.getSearchManager}} are not affected. > Empty results from queries from QueryFactory with offheap > --------------------------------------------------------- > > Key: ISPN-8337 > URL: https://issues.jboss.org/browse/ISPN-8337 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Affects Versions: 9.1.1.Final > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Fix For: 9.1.2.Final, 9.2.0.Alpha1 > > > When enabling Storage.OFF_HEAP or Storage.BINARY, queries obtained from {{Search.getQueryFactory}} return empty results. Queries build with Lucene from {{Search.getSearchManager}} are not affected. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 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 September 2017