[JBoss JIRA] (ISPN-8213) Functional commands are not replayed in tx on non-read owner
by Radim Vansa (JIRA)
[ https://issues.jboss.org/browse/ISPN-8213?page=com.atlassian.jira.plugin.... ]
Radim Vansa commented on ISPN-8213:
-----------------------------------
Transaction recovery is not working correctly either - when the node fetches remote values it applies all functional modifications that are currently in the transaction. When we do a recovery (EntryWrappingInterceptor.wrapEntriesForPrepareAndApply, isReplayEntryWrapping is set) and we remote-fetch a value, we apply **all** modifications (including those that are later in the modifications list).
> Functional commands are not replayed in tx on non-read owner
> ------------------------------------------------------------
>
> Key: ISPN-8213
> URL: https://issues.jboss.org/browse/ISPN-8213
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 9.1.0.Final
> Reporter: Radim Vansa
> Assignee: Radim Vansa
> Fix For: 9.4.0.Final
>
>
> When a functional command is executed on a node that is rebalancing and is not a read owner, we don't fetch the value (it does not end up in context's looked-up entries) but execute the command remotely in a read-only way.
> The entry should be later written on this node, too, but EWI tries to commit only looked-up entries.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (ISPN-7151) Migrate to Typescript 2.0
by Vladimir Blagojevic (JIRA)
[ https://issues.jboss.org/browse/ISPN-7151?page=com.atlassian.jira.plugin.... ]
Vladimir Blagojevic updated ISPN-7151:
--------------------------------------
Status: Resolved (was: Pull Request Sent)
Fix Version/s: 9.4.0.Alpha1
Resolution: Done
> Migrate to Typescript 2.0
> -------------------------
>
> Key: ISPN-7151
> URL: https://issues.jboss.org/browse/ISPN-7151
> Project: Infinispan
> Issue Type: Task
> Components: Console
> Affects Versions: 9.0.0.Alpha4
> Reporter: Ryan Emerson
> Assignee: Vladimir Blagojevic
> Priority: Minor
> Fix For: 9.4.0.Alpha1
>
>
> We should migrate from Typescript 1.x to 2.x. As well as many new features, the key benefit of such a transition is that it removes the need to utilises Typings as the ability to search/install t.ds files is now part of Typescript itself.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (ISPN-7151) Migrate to Typescript 2.0
by Vladimir Blagojevic (JIRA)
[ https://issues.jboss.org/browse/ISPN-7151?page=com.atlassian.jira.plugin.... ]
Vladimir Blagojevic updated ISPN-7151:
--------------------------------------
Status: Open (was: New)
> Migrate to Typescript 2.0
> -------------------------
>
> Key: ISPN-7151
> URL: https://issues.jboss.org/browse/ISPN-7151
> Project: Infinispan
> Issue Type: Task
> Components: Console
> Affects Versions: 9.0.0.Alpha4
> Reporter: Ryan Emerson
> Assignee: Vladimir Blagojevic
> Priority: Minor
>
> We should migrate from Typescript 1.x to 2.x. As well as many new features, the key benefit of such a transition is that it removes the need to utilises Typings as the ability to search/install t.ds files is now part of Typescript itself.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (ISPN-9256) Upgrade npm dependencies
by Vladimir Blagojevic (JIRA)
[ https://issues.jboss.org/browse/ISPN-9256?page=com.atlassian.jira.plugin.... ]
Vladimir Blagojevic updated ISPN-9256:
--------------------------------------
Status: Resolved (was: Pull Request Sent)
Fix Version/s: 9.4.0.Alpha1
Resolution: Done
> Upgrade npm dependencies
> ------------------------
>
> Key: ISPN-9256
> URL: https://issues.jboss.org/browse/ISPN-9256
> Project: Infinispan
> Issue Type: Task
> Components: Console
> Affects Versions: 9.3.0.CR1
> Reporter: Vladimir Blagojevic
> Assignee: Vladimir Blagojevic
> Fix For: 9.4.0.Alpha1
>
>
> Our project dependencies are getting very much out of date. We have not updated them since we started the project. Recently, we had an issue where a minor npm component upgrade in npm repo that our project uses caused an issue that took us hours to track down. After we upgrade all components, remove ever-increasing warnings, these issues should not happen anymore and we should have a much more resilient dependency tree.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months