[JBoss JIRA] (ISPN-7954) Cache.getCacheEntry clears created/lastUsed times before returning
by William Burns (JIRA)
William Burns created ISPN-7954:
-----------------------------------
Summary: Cache.getCacheEntry clears created/lastUsed times before returning
Key: ISPN-7954
URL: https://issues.jboss.org/browse/ISPN-7954
Project: Infinispan
Issue Type: Bug
Components: Core
Affects Versions: 9.1.0.Beta1, 9.0.1.Final
Reporter: William Burns
While writing a test for ISPN-7952 I found that due to the layers of wrapping and transformations of cache entry objects that the created and last used times will get cleared and set to 0. Do we care about user getting this data, and actually lastUsed would probably be the current time as it was just accessed.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (ISPN-4065) Refuse to store an index on an ASYNC Cache
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-4065?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes updated ISPN-4065:
------------------------------------
Fix Version/s: 9.0.2.Final
> Refuse to store an index on an ASYNC Cache
> ------------------------------------------
>
> Key: ISPN-4065
> URL: https://issues.jboss.org/browse/ISPN-4065
> Project: Infinispan
> Issue Type: Enhancement
> Components: Lucene Directory
> Affects Versions: 8.2.6.Final, 9.0.1.Final, 9.1.0.Beta1
> Reporter: Sanne Grinovero
> Assignee: Gustavo Fernandes
> Priority: Minor
> Labels: 64QueryBlockers, hackathon
> Fix For: 8.2.7.Final, 9.0.2.Final, 9.1.0.Final
>
>
> The Infinispan directory requires writing to the 3 caches, and cannot handle out-of-order operations that occur when ASYNC caches are used.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (ISPN-4065) Refuse to store an index on an ASYNC Cache
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-4065?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes updated ISPN-4065:
------------------------------------
Fix Version/s: 8.2.7.Final
> Refuse to store an index on an ASYNC Cache
> ------------------------------------------
>
> Key: ISPN-4065
> URL: https://issues.jboss.org/browse/ISPN-4065
> Project: Infinispan
> Issue Type: Enhancement
> Components: Lucene Directory
> Affects Versions: 8.2.6.Final, 9.0.1.Final, 9.1.0.Beta1
> Reporter: Sanne Grinovero
> Assignee: Gustavo Fernandes
> Priority: Minor
> Labels: 64QueryBlockers, hackathon
> Fix For: 8.2.7.Final, 9.1.0.Final
>
>
> The Infinispan directory requires writing to the 3 caches, and cannot handle out-of-order operations that occur when ASYNC caches are used.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (ISPN-4065) Refuse to store an index on an ASYNC Cache
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPN-4065?page=com.atlassian.jira.plugin.... ]
Gustavo Fernandes updated ISPN-4065:
------------------------------------
Affects Version/s: 9.0.1.Final
8.2.6.Final
> Refuse to store an index on an ASYNC Cache
> ------------------------------------------
>
> Key: ISPN-4065
> URL: https://issues.jboss.org/browse/ISPN-4065
> Project: Infinispan
> Issue Type: Enhancement
> Components: Lucene Directory
> Affects Versions: 8.2.6.Final, 9.0.1.Final, 9.1.0.Beta1
> Reporter: Sanne Grinovero
> Assignee: Gustavo Fernandes
> Priority: Minor
> Labels: 64QueryBlockers, hackathon
> Fix For: 9.1.0.Final
>
>
> The Infinispan directory requires writing to the 3 caches, and cannot handle out-of-order operations that occur when ASYNC caches are used.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (ISPN-4065) Refuse to store an index on an ASYNC Cache
by Adrian Nistor (JIRA)
[ https://issues.jboss.org/browse/ISPN-4065?page=com.atlassian.jira.plugin.... ]
Adrian Nistor updated ISPN-4065:
--------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
Integrated in master. Thanks [~gustavonalle]!
> Refuse to store an index on an ASYNC Cache
> ------------------------------------------
>
> Key: ISPN-4065
> URL: https://issues.jboss.org/browse/ISPN-4065
> Project: Infinispan
> Issue Type: Enhancement
> Components: Lucene Directory
> Affects Versions: 9.1.0.Beta1
> Reporter: Sanne Grinovero
> Assignee: Gustavo Fernandes
> Priority: Minor
> Labels: 64QueryBlockers, hackathon
> Fix For: 9.1.0.Final
>
>
> The Infinispan directory requires writing to the 3 caches, and cannot handle out-of-order operations that occur when ASYNC caches are used.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (ISPN-7884) StackOverflowException caused by GetAllCommand
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/ISPN-7884?page=com.atlassian.jira.plugin.... ]
Galder Zamarreño commented on ISPN-7884:
----------------------------------------
LOL, could not find this JIRA in the first place cos I searched for {{StackOverflowError}}. That's the correct name btw ;)
> StackOverflowException caused by GetAllCommand
> ----------------------------------------------
>
> Key: ISPN-7884
> URL: https://issues.jboss.org/browse/ISPN-7884
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 9.1.0.Alpha1
> Reporter: Radim Vansa
> Assignee: Radim Vansa
>
> GetAllCommand in BaseDistributionInterceptor handles all unsuccessful responses by throwing OutdatedTopologyException.
> BaseStateTransferInterceptor assumes that this is due to UnsureResponse in a scenario where it should be possible to retry the command immediately.
> If this occurs due to CacheNotFoundResponse (node being suspected) but before the availability mode is updated/consistent hash is updated with lost segments assigned to other nodes, the command is retried in a loop up to a point where the thread hits stack overflow.
> This does not affect regular cache.get() since this one throws AllOwnersLostException instead and this is treated differently in BaseStateTransferInterceptor.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (ISPN-7884) StackOverflowError caused by GetAllCommand
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/ISPN-7884?page=com.atlassian.jira.plugin.... ]
Galder Zamarreño updated ISPN-7884:
-----------------------------------
Summary: StackOverflowError caused by GetAllCommand (was: StackOverflowException caused by GetAllCommand)
> StackOverflowError caused by GetAllCommand
> ------------------------------------------
>
> Key: ISPN-7884
> URL: https://issues.jboss.org/browse/ISPN-7884
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 9.1.0.Alpha1
> Reporter: Radim Vansa
> Assignee: Radim Vansa
>
> GetAllCommand in BaseDistributionInterceptor handles all unsuccessful responses by throwing OutdatedTopologyException.
> BaseStateTransferInterceptor assumes that this is due to UnsureResponse in a scenario where it should be possible to retry the command immediately.
> If this occurs due to CacheNotFoundResponse (node being suspected) but before the availability mode is updated/consistent hash is updated with lost segments assigned to other nodes, the command is retried in a loop up to a point where the thread hits stack overflow.
> This does not affect regular cache.get() since this one throws AllOwnersLostException instead and this is treated differently in BaseStateTransferInterceptor.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months