March 2020 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-11563) Ensure we can use a non blocking thread pool for a blocking one with Loom

by Will Burns (Jira)

Will Burns created ISPN-11563: --------------------------------- Summary: Ensure we can use a non blocking thread pool for a blocking one with Loom Key: ISPN-11563 URL: https://issues.redhat.com/browse/ISPN-11563 Project: Infinispan Issue Type: Enhancement Components: Core Reporter: Will Burns Project Loom will add in Fibers and continuations. https://issues.redhat.com/browse/ISPN-11510 already adds in creating virtual threads. However we need to ensure that we can configure a system where the blocking and non blocking executors can point to the same thread pool since Loom will handle the continuation as needed. We will have to test if these keeps performance the same as well, since the blocking call will still stop that processing, it just can run a different operation while the blocking operation completes. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11543) Add BlockingHandler to simplify running blocking operations

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-11543?page=com.atlassian.jira.plugi... ] Will Burns updated ISPN-11543: ------------------------------ Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/8119 > Add BlockingHandler to simplify running blocking operations > ----------------------------------------------------------- > > Key: ISPN-11543 > URL: https://issues.redhat.com/browse/ISPN-11543 > Project: Infinispan > Issue Type: Sub-task > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 11.0.0.Dev04 > > > We have quite a few places that must run blocking operations that cannot be changed. These places must run the operation in a blocking thread and return on a non blocking thread. All of these places must register both a blocking and non blocking thread pool and properly handle them. This is both error prone and a lot of extra code. We should isolate this to a shared component which will in turn provide for an easier way to find such operations. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

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: Open (was: New) > 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)

6 years

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: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/8101 > 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)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-10673) Remove Cross-Site Replication from Local caches

by Pedro Ruivo (Jira)

[ https://issues.redhat.com/browse/ISPN-10673?page=com.atlassian.jira.plugi... ] Pedro Ruivo updated ISPN-10673: ------------------------------- Fix Version/s: 11.0.0.Dev04 > Remove Cross-Site Replication from Local caches > ----------------------------------------------- > > Key: ISPN-10673 > URL: https://issues.redhat.com/browse/ISPN-10673 > Project: Infinispan > Issue Type: Enhancement > Components: Cross-Site Replication > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Major > Fix For: 11.0.0.Dev04 > > > Currently, nothing prevents a local cache to have a site configured. However, this setup doesn't make much sense since we don't know to which node in the remote site the request is sent. (Except if the remote site only is a single node) > I believe it makes sense to remove it. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-10673) Remove Cross-Site Replication from Local caches

by Pedro Ruivo (Jira)

[ https://issues.redhat.com/browse/ISPN-10673?page=com.atlassian.jira.plugi... ] Pedro Ruivo updated ISPN-10673: ------------------------------- Status: Open (was: New) > Remove Cross-Site Replication from Local caches > ----------------------------------------------- > > Key: ISPN-10673 > URL: https://issues.redhat.com/browse/ISPN-10673 > Project: Infinispan > Issue Type: Enhancement > Components: Cross-Site Replication > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Major > Fix For: 11.0.0.Dev04 > > > Currently, nothing prevents a local cache to have a site configured. However, this setup doesn't make much sense since we don't know to which node in the remote site the request is sent. (Except if the remote site only is a single node) > I believe it makes sense to remove it. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-10673) Remove Cross-Site Replication from Local caches

by Pedro Ruivo (Jira)

[ https://issues.redhat.com/browse/ISPN-10673?page=com.atlassian.jira.plugi... ] Pedro Ruivo updated ISPN-10673: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/8125 > Remove Cross-Site Replication from Local caches > ----------------------------------------------- > > Key: ISPN-10673 > URL: https://issues.redhat.com/browse/ISPN-10673 > Project: Infinispan > Issue Type: Enhancement > Components: Cross-Site Replication > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Major > Fix For: 11.0.0.Dev04 > > > Currently, nothing prevents a local cache to have a site configured. However, this setup doesn't make much sense since we don't know to which node in the remote site the request is sent. (Except if the remote site only is a single node) > I believe it makes sense to remove it. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

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

by Will Burns (Jira)

Will Burns created ISPN-11561: --------------------------------- Summary: 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 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)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11560) Allow copy source code from document without markdown

by Donald Naro (Jira)

Donald Naro created ISPN-11560: ---------------------------------- Summary: Allow copy source code from document without markdown Key: ISPN-11560 URL: https://issues.redhat.com/browse/ISPN-11560 Project: Infinispan Issue Type: Enhancement Components: Documentation Affects Versions: 10.1.3.Final Reporter: Donald Naro Assignee: Donald Naro When copying source code from a document that has markdowns like : ( 1 ), ( 2 ) the markdowns are present in the clipboard. Example: {noformat} ConfigurationBuilder clientBuilder = new ConfigurationBuilder(); clientBuilder .addServer() .host("127.0.0.1") .port(11222) .security() .ssl() // Server SNI hostname. .sniHostName("myservername") 1 // Server certificate keystore. .trustStoreFileName("/path/to/truststore") 2 .trustStorePassword("truststorepassword".toCharArray()) // Client certificate keystore. .keyStoreFileName("/path/to/client/keystore") 3 .keyStorePassword("keystorepassword".toCharArray()); RemoteCache<String, String> cache=remoteCacheManager.getCache("secured"); {noformat} I would like to copy only the source code without 1, 2, 3 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (IPROTO-136) Avoid parsing and re-linking proto files, avoid re-registering identical marshallers

by Nistor Adrian (Jira)

[ https://issues.redhat.com/browse/IPROTO-136?page=com.atlassian.jira.plugi... ] Nistor Adrian updated IPROTO-136: --------------------------------- Fix Version/s: 4.3.3.Final 4.4.0.Alpha1 > Avoid parsing and re-linking proto files, avoid re-registering identical marshallers > ------------------------------------------------------------------------------------ > > Key: IPROTO-136 > URL: https://issues.redhat.com/browse/IPROTO-136 > Project: Infinispan ProtoStream > Issue Type: Enhancement > Affects Versions: 4.3.2.Final > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 4.3.3.Final, 4.4.0.Alpha1 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues March 2020