November 2017 - infinispan-issues

[JBoss JIRA] (ISPN-8466) Use StatefulSets in template

by Pedro Zapata (JIRA)

[ https://issues.jboss.org/browse/ISPN-8466?page=com.atlassian.jira.plugin.... ] Pedro Zapata updated ISPN-8466: ------------------------------- Sprint: Sprint #5 Nov 6th - Nov 24th 2 > Use StatefulSets in template > ---------------------------- > > Key: ISPN-8466 > URL: https://issues.jboss.org/browse/ISPN-8466 > Project: Infinispan > Issue Type: Enhancement > Components: Cloud Integrations > Reporter: Pedro Zapata > > Change deployment model from DeploymentConfig to StatefulSets, for symmetry, keeping the same behaviour in all services and stability. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7599) Add Jolokia to the server

by Pedro Zapata (JIRA)

[ https://issues.jboss.org/browse/ISPN-7599?page=com.atlassian.jira.plugin.... ] Pedro Zapata updated ISPN-7599: ------------------------------- Sprint: Sprint #5 Nov 6th - Nov 24th 2 > Add Jolokia to the server > ------------------------- > > Key: ISPN-7599 > URL: https://issues.jboss.org/browse/ISPN-7599 > Project: Infinispan > Issue Type: Feature Request > Components: Cloud Integrations, Server > Reporter: Sebastian Łaskawiec > Assignee: Vladimir Blagojevic > Priority: Critical > Fix For: 9.2.0.Final > > > The server should support exposing [Jolokia|https://jolokia.org] endpoints. The support should be disabled by default and there should be possibility to enable it using an environmental variable. > OpenShift has special Administration Console for Jolokia-enabled endpoints. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8402) Prevent rebalance

by Pedro Zapata (JIRA)

[ https://issues.jboss.org/browse/ISPN-8402?page=com.atlassian.jira.plugin.... ] Pedro Zapata updated ISPN-8402: ------------------------------- Sprint: Sprint #4 Oct 16th - Nov 6th, Sprint #5 Nov 6th - Nov 24th (was: Sprint #4 Oct 16th - Nov 6th, Sprint #5 Nov 6th - Nov 24th, Sprint #5 Nov 6th - Nov 24th 2) > Prevent rebalance > ----------------- > > Key: ISPN-8402 > URL: https://issues.jboss.org/browse/ISPN-8402 > Project: Infinispan > Issue Type: Feature Request > Components: Cloud Integrations, Core, State Transfer > Reporter: Sebastian Łaskawiec > Assignee: Dan Berindei > > Both Caching Service and Shared Memory Service require a way to prevent state transfer until the cluster is larger than "target" amount of nodes. > Note: A thing to consider during the design - we might want to have some timeout here. When we hit it, we might want to do the rebalance regardless to the number of nodes. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8500) Off-heap returns expited entries

by Vojtech Juranek (JIRA)

Vojtech Juranek created ISPN-8500: ------------------------------------- Summary: Off-heap returns expited entries Key: ISPN-8500 URL: https://issues.jboss.org/browse/ISPN-8500 Project: Infinispan Issue Type: Bug Components: Expiration, Off Heap Affects Versions: 9.2.0.Alpha2, 9.1.0.Final Reporter: Vojtech Juranek Assignee: Vojtech Juranek When expiration is turned on and off-heap is used, data container returns also entries which should be expired. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8396) Add interceptor preventing going out of memory

by Pedro Zapata (JIRA)

[ https://issues.jboss.org/browse/ISPN-8396?page=com.atlassian.jira.plugin.... ] Pedro Zapata reassigned ISPN-8396: ---------------------------------- Assignee: William Burns (was: Sebastian Łaskawiec) > Add interceptor preventing going out of memory > ---------------------------------------------- > > Key: ISPN-8396 > URL: https://issues.jboss.org/browse/ISPN-8396 > Project: Infinispan > Issue Type: Feature Request > Components: Cloud Integrations, Core > Reporter: Sebastian Łaskawiec > Assignee: William Burns > > We need an interceptor which will calculate the amount of required memory for PUT and report an error if that put will cause going out of memory. > Note that this is strictly connected to eviction mechanism (we might want to evict some entries on write) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8464) Calculate & adjust default persistence size

by Pedro Zapata (JIRA)

[ https://issues.jboss.org/browse/ISPN-8464?page=com.atlassian.jira.plugin.... ] Pedro Zapata updated ISPN-8464: ------------------------------- Priority: Minor (was: Major) > Calculate & adjust default persistence size > ------------------------------------------- > > Key: ISPN-8464 > URL: https://issues.jboss.org/browse/ISPN-8464 > Project: Infinispan > Issue Type: Enhancement > Components: Cloud Integrations > Reporter: Pedro Zapata > Assignee: Sebastian Łaskawiec > Priority: Minor > > There's a persistence volume claim of 1GiB. However, the amount of data to be stored for runtime info, given no cache store will be used, should be minimal. > Goal: get some measures of the expected amount of persistent space consumed and reduce the 1GiB claim to a more adjusted amount. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8395) Disable JMX duplicate domain by default

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-8395?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8395: ---------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.2.0.Beta1 Resolution: Done > Disable JMX duplicate domain by default > --------------------------------------- > > Key: ISPN-8395 > URL: https://issues.jboss.org/browse/ISPN-8395 > Project: Infinispan > Issue Type: Bug > Components: Configuration, JMX, reporting and management > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 9.2.0.Beta1, 9.2.0.Final > > > So that Infinispan can be more easily consumed out-of-the-box -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8396) Add interceptor preventing going out of memory

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-8396?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec reassigned ISPN-8396: ----------------------------------------- Assignee: Sebastian Łaskawiec > Add interceptor preventing going out of memory > ---------------------------------------------- > > Key: ISPN-8396 > URL: https://issues.jboss.org/browse/ISPN-8396 > Project: Infinispan > Issue Type: Feature Request > Components: Cloud Integrations, Core > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > > We need an interceptor which will calculate the amount of required memory for PUT and report an error if that put will cause going out of memory. > Note that this is strictly connected to eviction mechanism (we might want to evict some entries on write) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6879) Calculate (and expose) minimum number of nodes for data in Infinispan

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-6879?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec commented on ISPN-6879: ------------------------------------------- [~dan.berindei] oooh I guess I misunderstood you. I believe this type of information can be retrieved from Kubernetes API. Actually {{KUBE_PING}} does it to some extend: https://github.com/jgroups-extras/jgroups-kubernetes/blob/master/src/main... > Calculate (and expose) minimum number of nodes for data in Infinispan > --------------------------------------------------------------------- > > Key: ISPN-6879 > URL: https://issues.jboss.org/browse/ISPN-6879 > Project: Infinispan > Issue Type: Feature Request > Components: Cloud Integrations, Server > Reporter: Sebastian Łaskawiec > Assignee: William Burns > > With Kubernetes autoscaling we need to be able to tell what is the minimum amount of nodes necessary for hosting data (probably some sort of size + number of nodes estimation). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6879) Calculate (and expose) minimum number of nodes for data in Infinispan

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-6879?page=com.atlassian.jira.plugin.... ] Dan Berindei commented on ISPN-6879: ------------------------------------ [~sebastian.laskawiec] by "this automatic mechanism", do you mean contact OpenShift and detect how many nodes the user intends to keep up? > Calculate (and expose) minimum number of nodes for data in Infinispan > --------------------------------------------------------------------- > > Key: ISPN-6879 > URL: https://issues.jboss.org/browse/ISPN-6879 > Project: Infinispan > Issue Type: Feature Request > Components: Cloud Integrations, Server > Reporter: Sebastian Łaskawiec > Assignee: William Burns > > With Kubernetes autoscaling we need to be able to tell what is the minimum amount of nodes necessary for hosting data (probably some sort of size + number of nodes estimation). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues November 2017