May 2019 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-10029) Transactional invalidation cache with shared store prone to stale reads, even with FORCE_WRITE_LOCK

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-10029?page=com.atlassian.jira.plugin... ] Dan Berindei updated ISPN-10029: -------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/6846, https://github.com/infinispan/infinispan/pull/6886, https://github.com/infinispan/infinispan/pull/6887, https://github.com/infinispan/infinispan/pull/6993 (was: https://github.com/infinispan/infinispan/pull/6846, https://github.com/infinispan/infinispan/pull/6886, https://github.com/infinispan/infinispan/pull/6887) > Transactional invalidation cache with shared store prone to stale reads, even with FORCE_WRITE_LOCK > --------------------------------------------------------------------------------------------------- > > Key: ISPN-10029 > URL: https://issues.jboss.org/browse/ISPN-10029 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.3.6.Final, 9.4.11.Final, 10.0.0.Beta3 > Reporter: Paul Ferraro > Assignee: Dan Berindei > Priority: Critical > Fix For: 10.0.0.Beta4, 9.3.7.Final, 9.4.14.Final > > Attachments: InvalidationLockingTest.java > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-93) AutoProtoSchemaBuilder.schemaFilePath() is not handled correctly

by Nistor Adrian (Jira)

[ https://issues.jboss.org/browse/IPROTO-93?page=com.atlassian.jira.plugin.... ] Nistor Adrian updated IPROTO-93: -------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/protostream/pull/66 > AutoProtoSchemaBuilder.schemaFilePath() is not handled correctly > ---------------------------------------------------------------- > > Key: IPROTO-93 > URL: https://issues.jboss.org/browse/IPROTO-93 > Project: Infinispan ProtoStream > Issue Type: Bug > Affects Versions: 4.3.0.Alpha4 > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 4.3.0.Alpha6 > > > Current implementation is wrong in these aspects: > * the (optional) schemaFilePath together with schemaFileName should only be used for constructing the classloader resource path > * when computing the final resource path from schemaFilePath + schemaFileName should take into account eventual leading or trailing '/' and handle it gracefully > * the file path used for SerializationContext registration should be only based on schemaFileName, and should not be relative to schemaFilePath -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-93) AutoProtoSchemaBuilder.schemaFilePath() is not handled correctly

by Nistor Adrian (Jira)

[ https://issues.jboss.org/browse/IPROTO-93?page=com.atlassian.jira.plugin.... ] Nistor Adrian updated IPROTO-93: -------------------------------- Fix Version/s: 4.3.0.Alpha6 > AutoProtoSchemaBuilder.schemaFilePath() is not handled correctly > ---------------------------------------------------------------- > > Key: IPROTO-93 > URL: https://issues.jboss.org/browse/IPROTO-93 > Project: Infinispan ProtoStream > Issue Type: Bug > Affects Versions: 4.3.0.Alpha4 > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 4.3.0.Alpha6 > > > Current implementation is wrong in these aspects: > * the (optional) schemaFilePath together with schemaFileName should only be used for constructing the classloader resource path > * when computing the final resource path from schemaFilePath + schemaFileName should take into account eventual leading or trailing '/' and handle it gracefully > * the file path used for SerializationContext registration should be only based on schemaFileName, and should not be relative to schemaFilePath -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-93) AutoProtoSchemaBuilder.schemaFilePath() is not handled correctly

by Nistor Adrian (Jira)

Nistor Adrian created IPROTO-93: ----------------------------------- Summary: AutoProtoSchemaBuilder.schemaFilePath() is not handled correctly Key: IPROTO-93 URL: https://issues.jboss.org/browse/IPROTO-93 Project: Infinispan ProtoStream Issue Type: Bug Affects Versions: 4.3.0.Alpha4 Reporter: Nistor Adrian Current implementation is wrong in these aspects: * the (optional) schemaFilePath together with schemaFileName should only be used for constructing the classloader resource path * when computing the final resource path from schemaFilePath + schemaFileName should take into account eventual leading or trailing '/' and handle it gracefully * the file path used for SerializationContext registration should be only based on schemaFileName, and should not be relative to schemaFilePath -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-93) AutoProtoSchemaBuilder.schemaFilePath() is not handled correctly

by Nistor Adrian (Jira)

[ https://issues.jboss.org/browse/IPROTO-93?page=com.atlassian.jira.plugin.... ] Nistor Adrian updated IPROTO-93: -------------------------------- Status: Open (was: New) > AutoProtoSchemaBuilder.schemaFilePath() is not handled correctly > ---------------------------------------------------------------- > > Key: IPROTO-93 > URL: https://issues.jboss.org/browse/IPROTO-93 > Project: Infinispan ProtoStream > Issue Type: Bug > Affects Versions: 4.3.0.Alpha4 > Reporter: Nistor Adrian > Priority: Major > > Current implementation is wrong in these aspects: > * the (optional) schemaFilePath together with schemaFileName should only be used for constructing the classloader resource path > * when computing the final resource path from schemaFilePath + schemaFileName should take into account eventual leading or trailing '/' and handle it gracefully > * the file path used for SerializationContext registration should be only based on schemaFileName, and should not be relative to schemaFilePath -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-93) AutoProtoSchemaBuilder.schemaFilePath() is not handled correctly

by Nistor Adrian (Jira)

[ https://issues.jboss.org/browse/IPROTO-93?page=com.atlassian.jira.plugin.... ] Work on IPROTO-93 started by Nistor Adrian. ------------------------------------------- > AutoProtoSchemaBuilder.schemaFilePath() is not handled correctly > ---------------------------------------------------------------- > > Key: IPROTO-93 > URL: https://issues.jboss.org/browse/IPROTO-93 > Project: Infinispan ProtoStream > Issue Type: Bug > Affects Versions: 4.3.0.Alpha4 > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > > Current implementation is wrong in these aspects: > * the (optional) schemaFilePath together with schemaFileName should only be used for constructing the classloader resource path > * when computing the final resource path from schemaFilePath + schemaFileName should take into account eventual leading or trailing '/' and handle it gracefully > * the file path used for SerializationContext registration should be only based on schemaFileName, and should not be relative to schemaFilePath -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9722) Perform all CacheStore operations on a separate thread

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-9722?page=com.atlassian.jira.plugin.... ] Dan Berindei commented on ISPN-9722: ------------------------------------ [~william.burns] personally I'm a bit skeptical about using a separate thread pool: with the default {{CallerRunsPolicy}} we're always going to run some tasks in the caller thread, so it adds a lot of edge cases. And I wonder if we should make an exception when the store is asynchronous: blocking to wait for space in the write-behind queue is the same as blocking to wait for a free worker thread (or space in the thread pool queue). > Perform all CacheStore operations on a separate thread > ------------------------------------------------------ > > Key: ISPN-9722 > URL: https://issues.jboss.org/browse/ISPN-9722 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 10.0.0.Final > > > Persistence is one of the few remaining systems that are not non blocking. This needs to be remedied. We will eventually need to add an SPI that does this, but for now we need to offload the persistence operations to a different thread pool. > This should only require changes in the PersistenceManager to return non blocking methods (ie. return CompletionStage). We should then update references to use non blocking when possible. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9407) FunctionalMapImpl.create does not inherit cache settings for Expiration and Eviction

by Ben Gardner (Jira)

[ https://issues.jboss.org/browse/ISPN-9407?page=com.atlassian.jira.plugin.... ] Ben Gardner commented on ISPN-9407: ----------------------------------- Any idea when this might be fixed? > FunctionalMapImpl.create does not inherit cache settings for Expiration and Eviction > ------------------------------------------------------------------------------------ > > Key: ISPN-9407 > URL: https://issues.jboss.org/browse/ISPN-9407 > Project: Infinispan > Issue Type: Bug > Affects Versions: 9.1.7.Final, 9.3.1.Final > Reporter: Ben Gardner > Assignee: Galder Zamarreño > Priority: Major > > http://infinispan.org/docs/stable/user_guide/user_guide.html#functional_m... > FunctionalMapImpl.create() does not inherit cache settings for Expiration and Eviction. > Because of this, when adding the entries via the readwritemap, entries never expire. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10234) Remove SingletonCacheWriter

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10234?page=com.atlassian.jira.plugin... ] Tristan Tarrant reassigned ISPN-10234: -------------------------------------- Assignee: Will Burns > Remove SingletonCacheWriter > --------------------------- > > Key: ISPN-10234 > URL: https://issues.jboss.org/browse/ISPN-10234 > Project: Infinispan > Issue Type: Sub-task > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 10.0.0.Final > > > SingletonCacheWriter has been replaced by shared stores as primary owner does writes instead of the coordinator. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10234) Remove SingletonCacheWriter

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10234?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10234: ----------------------------------- Status: Open (was: New) > Remove SingletonCacheWriter > --------------------------- > > Key: ISPN-10234 > URL: https://issues.jboss.org/browse/ISPN-10234 > Project: Infinispan > Issue Type: Sub-task > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 10.0.0.Final > > > SingletonCacheWriter has been replaced by shared stores as primary owner does writes instead of the coordinator. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues May 2019