[JBoss JIRA] (ISPN-9852) Invocations waiting for a new topology should resume in parallel
by Dan Berindei (Jira)
[ https://issues.jboss.org/browse/ISPN-9852?page=com.atlassian.jira.plugin.... ]
Dan Berindei reassigned ISPN-9852:
----------------------------------
Assignee: Dan Berindei
> Invocations waiting for a new topology should resume in parallel
> ----------------------------------------------------------------
>
> Key: ISPN-9852
> URL: https://issues.jboss.org/browse/ISPN-9852
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 10.0.0.Alpha2, 9.4.5.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
>
> When a command requires a topology newer than the current topology, it uses {{StateTransferLock.transactionDataFuture()}} to wait for the newer topology. When the tx data is received for the newer topology, some (most?) of the waiting operations do not use a separate executor, instead they are all resumed on the thread that received the tx data. If some operations block (e.g. because of a store), it could take a very long time to finish all the blocked operations.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 9 months
[JBoss JIRA] (ISPN-9852) Invocations waiting for a new topology should resume in parallel
by Dan Berindei (Jira)
[ https://issues.jboss.org/browse/ISPN-9852?page=com.atlassian.jira.plugin.... ]
Dan Berindei updated ISPN-9852:
-------------------------------
Status: Open (was: New)
> Invocations waiting for a new topology should resume in parallel
> ----------------------------------------------------------------
>
> Key: ISPN-9852
> URL: https://issues.jboss.org/browse/ISPN-9852
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 10.0.0.Alpha2, 9.4.5.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
>
> When a command requires a topology newer than the current topology, it uses {{StateTransferLock.transactionDataFuture()}} to wait for the newer topology. When the tx data is received for the newer topology, some (most?) of the waiting operations do not use a separate executor, instead they are all resumed on the thread that received the tx data. If some operations block (e.g. because of a store), it could take a very long time to finish all the blocked operations.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 9 months
[JBoss JIRA] (ISPN-10022) Tx compute command updates are not written to stores
by Katia Aresti (Jira)
[ https://issues.jboss.org/browse/ISPN-10022?page=com.atlassian.jira.plugin... ]
Katia Aresti updated ISPN-10022:
--------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Tx compute command updates are not written to stores
> ----------------------------------------------------
>
> Key: ISPN-10022
> URL: https://issues.jboss.org/browse/ISPN-10022
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 9.4.8.Final, 10.0.0.Beta2
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 10.0.0.Beta3, 9.4.10.Final
>
>
> {{TxBatchUpdater}} collects the modifications from all the commands in a transaction in order to write them to the stores. However, it doesn't implement the {{visitCompute*}} commands, so it doesn't collect any modifications from {{compute()}}, {{computeIfAbsent()}}, and {{computeIfPresent()}}.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 9 months
[JBoss JIRA] (ISPN-9963) Restructure Documentation Titles
by Don Naro (Jira)
[ https://issues.jboss.org/browse/ISPN-9963?page=com.atlassian.jira.plugin.... ]
Don Naro updated ISPN-9963:
---------------------------
Sprint: JDG Sprint #25, JDG Sprint #26 (was: JDG Sprint #25)
> Restructure Documentation Titles
> --------------------------------
>
> Key: ISPN-9963
> URL: https://issues.jboss.org/browse/ISPN-9963
> Project: Infinispan
> Issue Type: Enhancement
> Components: Documentation-Core
> Reporter: Don Naro
> Assignee: Don Naro
> Priority: Major
>
> Restructure the layout of the documentation directory and set up new titles. Part 1 to adopt flexible customer content.
> The goal is to have a buildable set of titles created from existing content. The current chapter files from ISPN 9.x books are moved into the /topics directory where they can be divided into sections and topics (discrete units of reusable information).
> Also requires changes to the docs layout on the community website.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 9 months