February 2018 - infinispan-issues

[JBoss JIRA] (ISPN-7793) Expose Infinispan cluster deployed in OpenShift

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7793?page=com.atlassian.jira.plugin.... ] Tristan Tarrant commented on ISPN-7793: --------------------------------------- My preference here is to support this transparently using DNS. Each datagrid node should get assigned a resolvable hostname which is used as external-host in the hot rod server configuration. Client nodes will receive topology information through Hot Rod containing these host names. Client nodes which have direct visibility of the datagrid nodes will resolve their addresses directly. Client nodes which do not have direct visibility should have their DNS configured to remap the datagrid node names to the proxy addresses. > Expose Infinispan cluster deployed in OpenShift > ----------------------------------------------- > > Key: ISPN-7793 > URL: https://issues.jboss.org/browse/ISPN-7793 > Project: Infinispan > Issue Type: Feature Request > Components: Cloud > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > > Find a way to expose an existing cluster deployed on Kubernetes to the outside world. > Links: > * https://github.com/slaskawi/external-ip-proxy > * https://blog.fabric8.io/additional-kubernetes-controllers-from-fabric8-yo... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-8880) SoftIndexFileStore process returns nothing when fetchValues is false

by William Burns (JIRA)

William Burns created ISPN-8880: ----------------------------------- Summary: SoftIndexFileStore process returns nothing when fetchValues is false Key: ISPN-8880 URL: https://issues.jboss.org/browse/ISPN-8880 Project: Infinispan Issue Type: Bug Components: Loaders and Stores Affects Versions: 9.2.0.CR2 Reporter: William Burns The soft index store process method relies on the value being set to determine if an entry was removed or not. Unfortunately when fetchValues is set to false this is always unset, which means it will return nothing. The reason is because of the not null check on this line https://github.com/infinispan/infinispan/blob/e5958e36e3358b52095798044c0... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-8804) Add example quick-start for Clustered Locks

by Katia Aresti (JIRA)

[ https://issues.jboss.org/browse/ISPN-8804?page=com.atlassian.jira.plugin.... ] Katia Aresti updated ISPN-8804: ------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan-simple-tutorials/pull/44 > Add example quick-start for Clustered Locks > ------------------------------------------- > > Key: ISPN-8804 > URL: https://issues.jboss.org/browse/ISPN-8804 > Project: Infinispan > Issue Type: Enhancement > Components: Clustered Locks > Reporter: Katia Aresti > Assignee: Katia Aresti > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-8720) Implement test for REST with SSL configuration template

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-8720?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-8720: ----------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.2.0.Final Resolution: Done > Implement test for REST with SSL configuration template > ------------------------------------------------------- > > Key: ISPN-8720 > URL: https://issues.jboss.org/browse/ISPN-8720 > Project: Infinispan > Issue Type: Task > Components: Test Suite - Server > Affects Versions: 9.2.0.CR1 > Reporter: Vojtech Juranek > Assignee: Vojtech Juranek > Fix For: 9.2.0.Final > > > test for ISPN-7917 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-8180) Add key to WriteEntryView

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/ISPN-8180?page=com.atlassian.jira.plugin.... ] Radim Vansa updated ISPN-8180: ------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/5796 > Add key to WriteEntryView > ------------------------- > > Key: ISPN-8180 > URL: https://issues.jboss.org/browse/ISPN-8180 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Reporter: Radim Vansa > Assignee: Radim Vansa > Fix For: 9.2.0.Final > > > WriteOnlyKeyCommand should be able to simulate ComputeIfAbsentCommand without the conditional part (dropping the condition during when this is added to modifications list) and the signature for that command's remapping function is {{Function<K, V>}}. Therefore, we need to add key() to the WriteEntryView. This comes with no performance costs as the key is always at hand, no need to load it from anywhere. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-8180) Add key to WriteEntryView

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/ISPN-8180?page=com.atlassian.jira.plugin.... ] Radim Vansa updated ISPN-8180: ------------------------------ Status: Open (was: New) > Add key to WriteEntryView > ------------------------- > > Key: ISPN-8180 > URL: https://issues.jboss.org/browse/ISPN-8180 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Reporter: Radim Vansa > Assignee: Radim Vansa > Fix For: 9.2.0.Final > > > WriteOnlyKeyCommand should be able to simulate ComputeIfAbsentCommand without the conditional part (dropping the condition during when this is added to modifications list) and the signature for that command's remapping function is {{Function<K, V>}}. Therefore, we need to add key() to the WriteEntryView. This comes with no performance costs as the key is always at hand, no need to load it from anywhere. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-8822) Performance degradation when running Spark jobs

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/ISPN-8822?page=com.atlassian.jira.plugin.... ] Radim Vansa updated ISPN-8822: ------------------------------ Git Pull Request: https://github.com/infinispan/infinispan/pull/5765, https://github.com/infinispan/infinispan/pull/5795 (was: https://github.com/infinispan/infinispan/pull/5765) > Performance degradation when running Spark jobs > ----------------------------------------------- > > Key: ISPN-8822 > URL: https://issues.jboss.org/browse/ISPN-8822 > Project: Infinispan > Issue Type: Bug > Components: Hot Rod > Affects Versions: 9.2.0.CR2 > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Fix For: 9.2.0.CR3 > > > When trying to upgrade the [Spark connector |https://github.com/infinispan/infinispan-spark/] to use Infinispan 9.2.0.CR2, the test suite runs about 10x slower. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-8862) Iteration and stream operations with passivation disabled shouldn't use in memory

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-8862?page=com.atlassian.jira.plugin.... ] William Burns commented on ISPN-8862: ------------------------------------- Looking at this more, I think this is a bit more complicated. If we have all entries in memory that we have in the store, this change would cause a very big performance degredation in my testing with a SingleFileStore (45 op/s down to .67 op/s). This should be optionally done based on if off heap/store as binary/eviction/preload and other factors. This needs to be thought out more. > Iteration and stream operations with passivation disabled shouldn't use in memory > --------------------------------------------------------------------------------- > > Key: ISPN-8862 > URL: https://issues.jboss.org/browse/ISPN-8862 > Project: Infinispan > Issue Type: Enhancement > Reporter: William Burns > Assignee: William Burns > Fix For: 9.3.0.Final > > > When passivation is disabled all entries are assumed to be in the cache loader/store. We currently try to merge these together in a sloppy way [1]. This first reads in memory and then from the store and keeps all keys from in memory to exclude them from the store. Unfortunately the store still has to pull the entries even for the already read keys, but just ignores them. This leads to a lot of inefficiency and memory bloat. Instead we should just return the store entries as is when passivation is disabled. > [1] https://github.com/infinispan/infinispan/blob/master/core/src/main/java/o... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-8804) Add example quick-start for Clustered Locks

by Katia Aresti (JIRA)

[ https://issues.jboss.org/browse/ISPN-8804?page=com.atlassian.jira.plugin.... ] Work on ISPN-8804 started by Katia Aresti. ------------------------------------------ > Add example quick-start for Clustered Locks > ------------------------------------------- > > Key: ISPN-8804 > URL: https://issues.jboss.org/browse/ISPN-8804 > Project: Infinispan > Issue Type: Enhancement > Components: Clustered Locks > Reporter: Katia Aresti > Assignee: Katia Aresti > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-8804) Add example quick-start for Clustered Locks

by Katia Aresti (JIRA)

[ https://issues.jboss.org/browse/ISPN-8804?page=com.atlassian.jira.plugin.... ] Katia Aresti updated ISPN-8804: ------------------------------- Status: Open (was: New) > Add example quick-start for Clustered Locks > ------------------------------------------- > > Key: ISPN-8804 > URL: https://issues.jboss.org/browse/ISPN-8804 > Project: Infinispan > Issue Type: Enhancement > Components: Clustered Locks > Reporter: Katia Aresti > Assignee: Katia Aresti > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues February 2018