January 2020 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-11204) Response Collector addResponse value can be ignored

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-11204?page=com.atlassian.jira.plugi... ] Will Burns updated ISPN-11204: ------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/7775 > Response Collector addResponse value can be ignored > --------------------------------------------------- > > Key: ISPN-11204 > URL: https://issues.redhat.com/browse/ISPN-11204 > Project: Infinispan > Issue Type: Bug > Components: Core > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 11.0.0.Alpha1 > > > A ResponseCollector can return a non value from `addResponse` that is a sign that the response is complete. However it is possible to get a non null value from one response and get another response that has null and the `finish` value is used instead. We should make sure that when a non null value is returned via `addResponse` that its value is always used. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9082) Off Heap maxIdle expiration is not implemented

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-9082?page=com.atlassian.jira.plugin... ] Will Burns updated ISPN-9082: ----------------------------- Status: Open (was: New) > Off Heap maxIdle expiration is not implemented > ---------------------------------------------- > > Key: ISPN-9082 > URL: https://issues.redhat.com/browse/ISPN-9082 > Project: Infinispan > Issue Type: Bug > Components: Expiration, Off Heap > Affects Versions: 9.2.1.Final > Reporter: Will Burns > Priority: Major > Fix For: 11.0.0.Alpha1 > > > Due to the usage of read/write locks Off Heap cannot easily update the last access time of an off heap entry. It would have to release the read lock and try to acquire the write lock to then finally update the last access time of an object. We would also have to guarantee the address pointer hadn't changed between when the read and write lock were obtained, since the value could have changed during that time period. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9082) Off Heap maxIdle expiration is not implemented

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-9082?page=com.atlassian.jira.plugin... ] Will Burns updated ISPN-9082: ----------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/7775 > Off Heap maxIdle expiration is not implemented > ---------------------------------------------- > > Key: ISPN-9082 > URL: https://issues.redhat.com/browse/ISPN-9082 > Project: Infinispan > Issue Type: Bug > Components: Expiration, Off Heap > Affects Versions: 9.2.1.Final > Reporter: Will Burns > Priority: Major > Fix For: 11.0.0.Alpha1 > > > Due to the usage of read/write locks Off Heap cannot easily update the last access time of an off heap entry. It would have to release the read lock and try to acquire the write lock to then finally update the last access time of an object. We would also have to guarantee the address pointer hadn't changed between when the read and write lock were obtained, since the value could have changed during that time period. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9082) Off Heap maxIdle expiration is not implemented

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-9082?page=com.atlassian.jira.plugin... ] Will Burns updated ISPN-9082: ----------------------------- Fix Version/s: 11.0.0.Alpha1 > Off Heap maxIdle expiration is not implemented > ---------------------------------------------- > > Key: ISPN-9082 > URL: https://issues.redhat.com/browse/ISPN-9082 > Project: Infinispan > Issue Type: Bug > Components: Expiration, Off Heap > Affects Versions: 9.2.1.Final > Reporter: Will Burns > Priority: Major > Fix For: 11.0.0.Alpha1 > > > Due to the usage of read/write locks Off Heap cannot easily update the last access time of an off heap entry. It would have to release the read lock and try to acquire the write lock to then finally update the last access time of an object. We would also have to guarantee the address pointer hadn't changed between when the read and write lock were obtained, since the value could have changed during that time period. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9082) Off Heap maxIdle expiration is not implemented

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-9082?page=com.atlassian.jira.plugin... ] Will Burns reassigned ISPN-9082: -------------------------------- Assignee: Will Burns > Off Heap maxIdle expiration is not implemented > ---------------------------------------------- > > Key: ISPN-9082 > URL: https://issues.redhat.com/browse/ISPN-9082 > Project: Infinispan > Issue Type: Bug > Components: Expiration, Off Heap > Affects Versions: 9.2.1.Final > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 11.0.0.Alpha1 > > > Due to the usage of read/write locks Off Heap cannot easily update the last access time of an off heap entry. It would have to release the read lock and try to acquire the write lock to then finally update the last access time of an object. We would also have to guarantee the address pointer hadn't changed between when the read and write lock were obtained, since the value could have changed during that time period. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11208) Scattered Cache does not replicate metadata on state transfer

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-11208?page=com.atlassian.jira.plugi... ] Will Burns commented on ISPN-11208: ----------------------------------- This may be needed https://infinispan.zulipchat.com/#narrow/stream/118645-infinispan/topic/m... > Scattered Cache does not replicate metadata on state transfer > ------------------------------------------------------------- > > Key: ISPN-11208 > URL: https://issues.redhat.com/browse/ISPN-11208 > Project: Infinispan > Issue Type: Bug > Affects Versions: 10.0.0.Final > Reporter: Will Burns > Priority: Major > > The RemoteMetadata that is replicated to other nodes during scattered state transfer drops all the metadata information, other than the version. We should include all of it if possible. > https://github.com/infinispan/infinispan/blob/e4661c4e87ca6b31750bf3d7a91... > An idea is instead to wrap the old metadata in a new one. we should make sure to not rewrap a RemoteMetadata though and unwrap if necessary as the owner moves. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11208) Scattered Cache does not replicate metadata on state transfer

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-11208?page=com.atlassian.jira.plugi... ] Will Burns updated ISPN-11208: ------------------------------ Summary: Scattered Cache does not replicate metadata on state transfer (was: Scattered Cache does not replicate expiration metadata on state transfer) > Scattered Cache does not replicate metadata on state transfer > ------------------------------------------------------------- > > Key: ISPN-11208 > URL: https://issues.redhat.com/browse/ISPN-11208 > Project: Infinispan > Issue Type: Bug > Affects Versions: 10.0.0.Final > Reporter: Will Burns > Priority: Major > > The RemoteMetadata that is replicated to other nodes during scattered state transfer drops all the metadata information, other than the version. We should include all of it if possible. > https://github.com/infinispan/infinispan/blob/e4661c4e87ca6b31750bf3d7a91... > An idea is instead to wrap the old metadata in a new one. we should make sure to not rewrap a RemoteMetadata though and unwrap if necessary as the owner moves. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11208) Scattered Cache does not replicate expiration metadata on state transfer

by Will Burns (Jira)

Will Burns created ISPN-11208: --------------------------------- Summary: Scattered Cache does not replicate expiration metadata on state transfer Key: ISPN-11208 URL: https://issues.redhat.com/browse/ISPN-11208 Project: Infinispan Issue Type: Bug Affects Versions: 10.0.0.Final Reporter: Will Burns The RemoteMetadata that is replicated to other nodes during scattered state transfer drops all the metadata information, other than the version. We should include all of it if possible. https://github.com/infinispan/infinispan/blob/e4661c4e87ca6b31750bf3d7a91... An idea is instead to wrap the old metadata in a new one. we should make sure to not rewrap a RemoteMetadata though and unwrap if necessary as the owner moves. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11207) Fancier cache creation for quickstarts

by Katia Aresti (Jira)

Katia Aresti created ISPN-11207: ----------------------------------- Summary: Fancier cache creation for quickstarts Key: ISPN-11207 URL: https://issues.redhat.com/browse/ISPN-11207 Project: Infinispan Issue Type: Feature Request Components: Hot Rod Affects Versions: 10.1.1.Final Reporter: Katia Aresti Today in client/server mode, to create caches on the fly, we need to pass XML template. This is not very pretty to be used on quickstarts. Make already defined templates names available in the administration API so they can be referenced in a simple way -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10617) Operator Docs: Getting started with k8s/OpenShift

by Donald Naro (Jira)

[ https://issues.redhat.com/browse/ISPN-10617?page=com.atlassian.jira.plugi... ] Donald Naro closed ISPN-10617. ------------------------------ Release Notes Text: Not an upstream issue. Fixed with JDG-3449. Resolution: Rejected > Operator Docs: Getting started with k8s/OpenShift > ------------------------------------------------- > > Key: ISPN-10617 > URL: https://issues.redhat.com/browse/ISPN-10617 > Project: Infinispan > Issue Type: Task > Components: Documentation > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > > assembly with getting started that includes procedure to setup pull request tokens. this should be done when engineering starts the work to create the cache service and dg service via the operator as well as the different profiles. > clarify details about creating the operator. requires kubeadmin to install the operator into specific namespaces. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues January 2020