October 2019 - infinispan-issues - Jboss List Archives

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

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10075?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10075: ----------------------------------- Fix Version/s: 10.0.1.Final (was: 10.0.0.Final) > We should ensure that when CompletionStages are completed they are continued only on Infinispan threads > ------------------------------------------------------------------------------------------------------- > > Key: ISPN-10075 > URL: https://issues.jboss.org/browse/ISPN-10075 > Project: Infinispan > Issue Type: Sub-task > Components: Core > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 10.0.1.Final > > > 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)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10062) Docs refer to infinispan-cli-server instead of infinispan-cli-interpreter

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10062?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10062: ----------------------------------- Fix Version/s: 10.0.1.Final (was: 10.0.0.Final) > Docs refer to infinispan-cli-server instead of infinispan-cli-interpreter > ------------------------------------------------------------------------- > > Key: ISPN-10062 > URL: https://issues.jboss.org/browse/ISPN-10062 > Project: Infinispan > Issue Type: Task > Components: Documentation-Core > Affects Versions: 9.4.10.Final, 10.0.0.Beta2 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 9.4.17.Final, 10.0.1.Final > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10362) Unify remove command initialization and invocation

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10362?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10362: ----------------------------------- Fix Version/s: 10.0.1.Final (was: 10.0.0.Final) > Unify remove command initialization and invocation > -------------------------------------------------- > > Key: ISPN-10362 > URL: https://issues.jboss.org/browse/ISPN-10362 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Affects Versions: 10.0.0.Beta3 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 10.0.1.Final > > > ISPN-10322 unified command initialization with {{InitializableCommand}}, but we should go further and unify initialization with invocation. > We can replace the current {{ReplicableCommand.invokeAsync}} and {{InitializableCommand.init(ComponentRegistry()}} methods with a method {{CacheRpcCommand.invokeAsync(ComponentRegistry)}} (or maybe {{execute}}?). > For global commands we can create a {{GlobalRpcCommand}} interface with a method {{invokeAsync(GlobalComponentRegistry)}}. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10356) Create Quarkus extension that can run LOCAL cache in Quarkus

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10356?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10356: ----------------------------------- Fix Version/s: 10.0.1.Final (was: 10.0.0.Final) > Create Quarkus extension that can run LOCAL cache in Quarkus > ------------------------------------------------------------ > > Key: ISPN-10356 > URL: https://issues.jboss.org/browse/ISPN-10356 > Project: Infinispan > Issue Type: Sub-task > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 10.0.1.Final > > > The first step should be just to get a LOCAL cache working as a Quarkus extension. This should allow us to get quite a bit of work done without leaving the Quarkus ecosystem. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10355) Run Infinispan Server on Quarkus

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10355?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10355: ----------------------------------- Fix Version/s: 10.0.1.Final (was: 10.0.0.Final) > Run Infinispan Server on Quarkus > -------------------------------- > > Key: ISPN-10355 > URL: https://issues.jboss.org/browse/ISPN-10355 > Project: Infinispan > Issue Type: Feature Request > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 10.0.1.Final > > > We need to allow the Infinispan Server to run on Quarkus. See nested issues for more specifics. > It may be required to have this run outside of Quarkus as it doesn't yet support a Command Mode. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10339) Investigate and Rework Multiple Cache Loaders Support

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10339?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10339: ----------------------------------- Fix Version/s: 10.0.1.Final (was: 10.0.0.Final) > Investigate and Rework Multiple Cache Loaders Support > ----------------------------------------------------- > > Key: ISPN-10339 > URL: https://issues.jboss.org/browse/ISPN-10339 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores > Reporter: Will Burns > Priority: Major > Fix For: 10.0.1.Final > > > Today having more than one loader configured is possible. However the way it operates is not well defined or even documented. > Currently for single key operations we try each loader one by one until one returns non null. For writes we write to all stores. However for bulk operations we only load from the first AdvancedLoader. This can be a bit confusing how these are done, but makes sense at least when thought about. > The other concern that is new is now that we have segmented loaders that perform better under bulk operations that their non segmented counterparts. ISPN-9816 makes it better, however its checking is not the most foolproof. We may want to instead explicitly find per invocation if the current loader is segmented or not before invoking the appropriate method. Currently we only check at startup if any loader is segmented; however this can be problematic if the first loader is not segmented and not advanced or handle the case of a loader being removed at runtime. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10324) Create a "tools" distribution

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10324?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10324: ----------------------------------- Fix Version/s: 10.0.1.Final (was: 10.0.0.Final) > Create a "tools" distribution > ----------------------------- > > Key: ISPN-10324 > URL: https://issues.jboss.org/browse/ISPN-10324 > Project: Infinispan > Issue Type: Task > Components: Build > Affects Versions: 10.0.0.Beta3 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.0.1.Final > > > With the removal of all "embedded" distributions (ISPN-10274) we no longer have a distribution for "tools" such as the cache store migrator, et al. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10311) Remove all the blocking Transport methods

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10311?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10311: ----------------------------------- Fix Version/s: 10.0.1.Final (was: 10.0.0.Final) > Remove all the blocking Transport methods > ----------------------------------------- > > Key: ISPN-10311 > URL: https://issues.jboss.org/browse/ISPN-10311 > Project: Infinispan > Issue Type: Sub-task > Components: Core > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 10.0.1.Final > > > The Transport class has many blocking methods on it that have been deprecated. This class was never public as it doesn't have a package-info.java, thus we can remove these methods at will. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10310) State Transfer needs to be made non blocking

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10310?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10310: ----------------------------------- Fix Version/s: 10.0.1.Final (was: 10.0.0.Final) > State Transfer needs to be made non blocking > -------------------------------------------- > > Key: ISPN-10310 > URL: https://issues.jboss.org/browse/ISPN-10310 > Project: Infinispan > Issue Type: Sub-task > Components: Core, State Transfer > Reporter: Will Burns > Assignee: Dan Berindei > Priority: Major > Fix For: 10.0.1.Final > > > State Transfer currently invokes many methods that are non blocking and blocks to wait for those to complete. We need to ensure that all the various usages are converted to be non blocking and when absolutely not possible convert them to using a separate thread pool. The final goal is to eventually eliminate the state transfer thread pool as well. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10301) Deprecate server media type application/x-java-object

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10301?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10301: ----------------------------------- Fix Version/s: 10.0.1.Final (was: 10.0.0.Final) > Deprecate server media type application/x-java-object > ----------------------------------------------------- > > Key: ISPN-10301 > URL: https://issues.jboss.org/browse/ISPN-10301 > Project: Infinispan > Issue Type: Task > Components: Server > Affects Versions: 10.0.0.Beta3 > Reporter: Dan Berindei > Priority: Major > Fix For: 10.0.1.Final > > > `application/x-java-object` needs to have the application classes deployed on the server in order to do anything useful with it, and the server must also be able to do reflection on those application classes. > We should steer users towards always using `application/x-protostream` instead, because the protobuf schemas are much easier to deploy to the server. The first step would be to make protostream the default marshalling mechanism in the client. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 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 October 2019