April 2020 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-11758) QueryCache is a global component but should scope all cached queries per cache

by Nistor Adrian (Jira)

[ https://issues.redhat.com/browse/ISPN-11758?page=com.atlassian.jira.plugi... ] Nistor Adrian updated ISPN-11758: --------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/8270 > QueryCache is a global component but should scope all cached queries per cache > ------------------------------------------------------------------------------ > > Key: ISPN-11758 > URL: https://issues.redhat.com/browse/ISPN-11758 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying, Remote Querying > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 11.0.0.Dev05 > > > The query might execute differently depending on the configuration of each cache. This will be an issue starting with HSearch 6. > All entries will be keyed also based on cache name. QueryCache must be cleared when a cache stops. Also, all caches must have a configured stop dependency on the QueryCache. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11757) Do not allow multiple indexing providers per cache

by Nistor Adrian (Jira)

[ https://issues.redhat.com/browse/ISPN-11757?page=com.atlassian.jira.plugi... ] Nistor Adrian updated ISPN-11757: --------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/8270 (was: https://github.com/infinispan/infinispan/pull/8268) > Do not allow multiple indexing providers per cache > -------------------------------------------------- > > Key: ISPN-11757 > URL: https://issues.redhat.com/browse/ISPN-11757 > Project: Infinispan > Issue Type: Task > Components: Embedded Querying, Remote Querying > Affects Versions: 11.0.0.Alpha1 > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 11.0.0.Dev05 > > > Mixing multiple providers creates many complications and will no longer be accepted since 11 and the migration to HSearch 6 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11496) Add entry

by Katia Aresti (Jira)

[ https://issues.redhat.com/browse/ISPN-11496?page=com.atlassian.jira.plugi... ] Katia Aresti updated ISPN-11496: -------------------------------- Status: Open (was: New) > Add entry > --------- > > Key: ISPN-11496 > URL: https://issues.redhat.com/browse/ISPN-11496 > Project: Infinispan > Issue Type: Feature Request > Components: Console > Affects Versions: 10.1.5.Final > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Major > Labels: console-ng > Fix For: 11.0.0.Final > > > When we click in the Add entry button > Pop is displayed with a form to add an entry > https://marvelapp.com/6j85bdb/screen/66827517 > When the add button is added, we come back to the list and we display a message and the action is displayed in the recent activity console > https://marvelapp.com/6j85bdb/screen/66827519 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11607) Fix blocking LimitedExecutor#addPermit test failures

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-11607?page=com.atlassian.jira.plugi... ] Will Burns updated ISPN-11607: ------------------------------ Status: Open (was: New) > Fix blocking LimitedExecutor#addPermit test failures > ---------------------------------------------------- > > Key: ISPN-11607 > URL: https://issues.redhat.com/browse/ISPN-11607 > Project: Infinispan > Issue Type: Sub-task > Components: Core > Reporter: Will Burns > Priority: Major > > Blocking detection can fail spuriously such as https://ci.infinispan.org/job/Infinispan/job/PR-8174/1/testReport/junit/o... > We should fix the code or add an exception for it, most likely the latter. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11607) Fix blocking LimitedExecutor#addPermit test failures

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-11607?page=com.atlassian.jira.plugi... ] Will Burns updated ISPN-11607: ------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/8269 > Fix blocking LimitedExecutor#addPermit test failures > ---------------------------------------------------- > > Key: ISPN-11607 > URL: https://issues.redhat.com/browse/ISPN-11607 > Project: Infinispan > Issue Type: Sub-task > Components: Core > Reporter: Will Burns > Priority: Major > > Blocking detection can fail spuriously such as https://ci.infinispan.org/job/Infinispan/job/PR-8174/1/testReport/junit/o... > We should fix the code or add an exception for it, most likely the latter. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11561) Remove extra thread in BlockingTaskAwareExecutorServiceImpl

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-11561?page=com.atlassian.jira.plugi... ] Will Burns updated ISPN-11561: ------------------------------ Status: Resolved (was: Pull Request Sent) Fix Version/s: 11.0.0.Dev04 (was: 11.0.0.Dev05) Resolution: Done > Remove extra thread in BlockingTaskAwareExecutorServiceImpl > ----------------------------------------------------------- > > Key: ISPN-11561 > URL: https://issues.redhat.com/browse/ISPN-11561 > Project: Infinispan > Issue Type: Sub-task > Components: Core > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 11.0.0.Dev04 > > > The BlockingTaskAwareExecutorServiceImpl spawns a controller thread to handle requests. We should be able to remove that thread and instead use an idea similar to rxjava with processing in a single invoked thread instead as the operations it spawns are non blocking. > We should also optimize calls to avoid O(n) calls like size. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11533) Convert ClientListenerRegistry to use non blocking calls

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-11533?page=com.atlassian.jira.plugi... ] Will Burns updated ISPN-11533: ------------------------------ Status: Resolved (was: Pull Request Sent) Fix Version/s: 11.0.0.Dev04 Resolution: Done > Convert ClientListenerRegistry to use non blocking calls > -------------------------------------------------------- > > Key: ISPN-11533 > URL: https://issues.redhat.com/browse/ISPN-11533 > Project: Infinispan > Issue Type: Sub-task > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 11.0.0.Dev04 > > > The ClientListenerRegistry currently invokes the blocking addListener methods. This should use the non blocking methods and not use the blocking thread pool. > Note this issue will require https://issues.redhat.com/browse/ISPN-10457 to be fixed first so that initial state is truly non blocking. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8955) ClusterTopologyManagerImpl should only use non-blocking RPCs

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-8955?page=com.atlassian.jira.plugin... ] Will Burns resolved ISPN-8955. ------------------------------ Resolution: Duplicate Issue This was fixed in ISPN-10310 > ClusterTopologyManagerImpl should only use non-blocking RPCs > ------------------------------------------------------------ > > Key: ISPN-8955 > URL: https://issues.redhat.com/browse/ISPN-8955 > Project: Infinispan > Issue Type: Task > Components: Core > Affects Versions: 9.2.0.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > > {{ClusterTopologyManagerImpl}} still uses some blocking RPCs, particularly when a node becomes coordinator or after a merge. It should use non-blocking RPCs instead. > It could also use non-blocking RPCs instead of fire-and-forget messages for things like topology updates, which would allow delivering topology updates in the same order on all the nodes instead of having regular nodes make to with missing topology updates (when the coordinator doesn't change). -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11552) Cluster Locks should be non blocking

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-11552?page=com.atlassian.jira.plugi... ] Will Burns resolved ISPN-11552. ------------------------------- Resolution: Duplicate Issue This was handled in https://issues.redhat.com/browse/ISPN-11740 > Cluster Locks should be non blocking > ------------------------------------ > > Key: ISPN-11552 > URL: https://issues.redhat.com/browse/ISPN-11552 > Project: Infinispan > Issue Type: Sub-task > Components: Clustered Locks > Reporter: Will Burns > Priority: Major > > Cluster Locks currently use a blocking executor to process lock and unlock calls. The API for these methods are non blocking and we should ensure they do not block down the stack. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10075) We should ensure that when CompletionStages are completed they are continued only on Infinispan threads

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-10075?page=com.atlassian.jira.plugi... ] Will Burns resolved ISPN-10075. ------------------------------- Resolution: Duplicate Issue This was handled in https://issues.redhat.com/browse/ISPN-11543 > We should ensure that when CompletionStages are completed they are continued only on Infinispan threads > ------------------------------------------------------------------------------------------------------- > > Key: ISPN-10075 > URL: https://issues.redhat.com/browse/ISPN-10075 > Project: Infinispan > Issue Type: Sub-task > Components: Core > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > > When a user can supply a CompletionStage to delay operations this can cause a possibility of that being completed on a different thread than expected. The new non blocking listeners will especially be affected by this (ISPN-9614). This is also problematic for CacheLoader SPI and any future API that takes a Publisher as an argument from the user. > This issue should at least fix the upcoming non blocking listeners as discussed at https://github.com/infinispan/infinispan/pull/6401#issuecomment-475181484. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues April 2020