November 2018 - infinispan-issues

[JBoss JIRA] (ISPN-9733) Proposal for 10 Documentation Restructure

by Don Naro (Jira)

Don Naro created ISPN-9733: ------------------------------ Summary: Proposal for 10 Documentation Restructure Key: ISPN-9733 URL: https://issues.jboss.org/browse/ISPN-9733 Project: Infinispan Issue Type: Enhancement Components: Documentation-Core Affects Versions: 10.0.0.Alpha2 Reporter: Don Naro Assignee: Don Naro Fix For: 10.0.0.Final Don to create a detailed proposal for restructuring the ISPN documentation library. New organization for content. Present proposal to team and review. Outcome should be clear idea of what we want to deliver and then breaking it down into tasks. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-9732) Local iteration optimization with write behind is valid for non shared stores

by William Burns (Jira)

[ https://issues.jboss.org/browse/ISPN-9732?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-9732: -------------------------------- Fix Version/s: 9.4.2.Final 10.0.0.Alpha1 > Local iteration optimization with write behind is valid for non shared stores > ----------------------------------------------------------------------------- > > Key: ISPN-9732 > URL: https://issues.jboss.org/browse/ISPN-9732 > Project: Infinispan > Issue Type: Bug > Components: Core, Loaders and Stores > Affects Versions: 9.4.1.Final > Reporter: William Burns > Assignee: William Burns > Priority: Major > Fix For: 9.4.2.Final, 10.0.0.Alpha1 > > > ISPN-9332 disabled iteration optimization when an async store is present. This is only required for shared stores, since non shared stores will write to the async store on each node. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-9732) Local iteration optimization with write behind is valid for non shared stores

by William Burns (Jira)

[ https://issues.jboss.org/browse/ISPN-9732?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-9732: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/6420, https://github.com/infinispan/infinispan/pull/6421 > Local iteration optimization with write behind is valid for non shared stores > ----------------------------------------------------------------------------- > > Key: ISPN-9732 > URL: https://issues.jboss.org/browse/ISPN-9732 > Project: Infinispan > Issue Type: Bug > Components: Core, Loaders and Stores > Affects Versions: 9.4.1.Final > Reporter: William Burns > Assignee: William Burns > Priority: Major > Fix For: 9.4.2.Final, 10.0.0.Alpha1 > > > ISPN-9332 disabled iteration optimization when an async store is present. This is only required for shared stores, since non shared stores will write to the async store on each node. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-4075) State transfer should preserve the creation timestamp of entries

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-4075?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-4075: ---------------------------------- Sprint: Sprint 10.0.0.Beta1 > State transfer should preserve the creation timestamp of entries > ---------------------------------------------------------------- > > Key: ISPN-4075 > URL: https://issues.jboss.org/browse/ISPN-4075 > Project: Infinispan > Issue Type: Feature Request > Components: Core > Affects Versions: 6.0.1.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 10.0.0.Final > > > State transfer inserts values with the current time as the creation time. Since the entries store the expected lifespan and not the expected expiration time, entries on the receiving node could expire much later than intended. > The argument probably doesn't apply to the timestamp of the last usage. Since state transfer process could be interpreted as a reader, it should be fine to extend the update the time of the last usage both on the sending node and on the receiving node. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-4075) State transfer should preserve the creation timestamp of entries

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-4075?page=com.atlassian.jira.plugin.... ] Tristan Tarrant reassigned ISPN-4075: ------------------------------------- Assignee: Dan Berindei > State transfer should preserve the creation timestamp of entries > ---------------------------------------------------------------- > > Key: ISPN-4075 > URL: https://issues.jboss.org/browse/ISPN-4075 > Project: Infinispan > Issue Type: Feature Request > Components: Core > Affects Versions: 6.0.1.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 10.0.0.Final > > > State transfer inserts values with the current time as the creation time. Since the entries store the expected lifespan and not the expected expiration time, entries on the receiving node could expire much later than intended. > The argument probably doesn't apply to the timestamp of the last usage. Since state transfer process could be interpreted as a reader, it should be fine to extend the update the time of the last usage both on the sending node and on the receiving node. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-9332) REPL local iteration optimization cannot be used when store has write behind

by William Burns (Jira)

[ https://issues.jboss.org/browse/ISPN-9332?page=com.atlassian.jira.plugin.... ] William Burns commented on ISPN-9332: ------------------------------------- I created ISPN-9732 for it. > REPL local iteration optimization cannot be used when store has write behind > ---------------------------------------------------------------------------- > > Key: ISPN-9332 > URL: https://issues.jboss.org/browse/ISPN-9332 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores, Streams > Affects Versions: 9.3.0.Final > Reporter: William Burns > Assignee: William Burns > Priority: Major > Fix For: 9.4.0.CR3 > > > When write behind is enabled, the write modification is stored on the primary owner. REPL local iteration can read from non owned data, thus causing an inconsistency. > Thus distributed streams should always go remote when not all segments are primarily owned on a given node when write behind is enabled. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-9732) Local iteration optimization with write behind is valid for non shared stores

by William Burns (Jira)

[ https://issues.jboss.org/browse/ISPN-9732?page=com.atlassian.jira.plugin.... ] William Burns updated ISPN-9732: -------------------------------- Status: Open (was: New) > Local iteration optimization with write behind is valid for non shared stores > ----------------------------------------------------------------------------- > > Key: ISPN-9732 > URL: https://issues.jboss.org/browse/ISPN-9732 > Project: Infinispan > Issue Type: Bug > Components: Core, Loaders and Stores > Affects Versions: 9.4.1.Final > Reporter: William Burns > Assignee: William Burns > Priority: Major > > ISPN-9332 disabled iteration optimization when an async store is present. This is only required for shared stores, since non shared stores will write to the async store on each node. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-9732) Local iteration optimization with write behind is valid for non shared stores

by William Burns (Jira)

William Burns created ISPN-9732: ----------------------------------- Summary: Local iteration optimization with write behind is valid for non shared stores Key: ISPN-9732 URL: https://issues.jboss.org/browse/ISPN-9732 Project: Infinispan Issue Type: Bug Components: Core, Loaders and Stores Affects Versions: 9.4.1.Final Reporter: William Burns Assignee: William Burns ISPN-9332 disabled iteration optimization when an async store is present. This is only required for shared stores, since non shared stores will write to the async store on each node. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-9332) REPL local iteration optimization cannot be used when store has write behind

by William Burns (Jira)

[ https://issues.jboss.org/browse/ISPN-9332?page=com.atlassian.jira.plugin.... ] William Burns commented on ISPN-9332: ------------------------------------- Hrmm, I concur. This should only be needed for shared stores with REPL. > REPL local iteration optimization cannot be used when store has write behind > ---------------------------------------------------------------------------- > > Key: ISPN-9332 > URL: https://issues.jboss.org/browse/ISPN-9332 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores, Streams > Affects Versions: 9.3.0.Final > Reporter: William Burns > Assignee: William Burns > Priority: Major > Fix For: 9.4.0.CR3 > > > When write behind is enabled, the write modification is stored on the primary owner. REPL local iteration can read from non owned data, thus causing an inconsistency. > Thus distributed streams should always go remote when not all segments are primarily owned on a given node when write behind is enabled. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-9731) SpringRemoteCacheManager.getWriteTimeout returns readTimeout

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-9731?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-9731: ------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > SpringRemoteCacheManager.getWriteTimeout returns readTimeout > ------------------------------------------------------------ > > Key: ISPN-9731 > URL: https://issues.jboss.org/browse/ISPN-9731 > Project: Infinispan > Issue Type: Bug > Components: Spring Integration > Affects Versions: 9.4.1.Final > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 9.4.2.Final, 10.0.0.Alpha1 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues November 2018