[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:
-------------------------------
Sprint: Sprint #5 Nov 6th - Nov 24th, Sprint #5 Nov 6th - Nov 24th 2 (was: Sprint #5 Nov 6th - Nov 24th)
> 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
>
> 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)
8 years, 5 months
[JBoss JIRA] (ISPN-8402) Prevent rebalance
by Sebastian Łaskawiec (JIRA)
[ https://issues.jboss.org/browse/ISPN-8402?page=com.atlassian.jira.plugin.... ]
Sebastian Łaskawiec updated ISPN-8402:
--------------------------------------
Sprint: Sprint #4 Oct 16th - Nov 6th, Sprint #5 Nov 6th - Nov 24th, Sprint #5 Nov 6th - Nov 24th 2 (was: Sprint #4 Oct 16th - Nov 6th, Sprint #5 Nov 6th - Nov 24th)
> 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)
8 years, 5 months
[JBoss JIRA] (ISPN-8452) KUBE_PING doesn't work with JDG 7.2 OpenShift image
by Sebastian Łaskawiec (JIRA)
[ https://issues.jboss.org/browse/ISPN-8452?page=com.atlassian.jira.plugin.... ]
Sebastian Łaskawiec updated ISPN-8452:
--------------------------------------
Sprint: Sprint #5 Nov 6th - Nov 24th, Sprint #5 Nov 6th - Nov 24th 2 (was: Sprint #5 Nov 6th - Nov 24th)
> KUBE_PING doesn't work with JDG 7.2 OpenShift image
> ---------------------------------------------------
>
> Key: ISPN-8452
> URL: https://issues.jboss.org/browse/ISPN-8452
> Project: Infinispan
> Issue Type: Bug
> Components: Cloud Integrations
> Reporter: Sebastian Łaskawiec
> Assignee: Ryan Emerson
> Priority: Blocker
>
> It seems that KUBE_PING doesn't work with the latest version of JDG 7.2 OpenShift image. The reason for this is that JDG 7.2 is shipped with upstream KUBE_PING which conflicts with the one provided in the openshift layer.
> The easiest solution is to revert layer ordering {{layers.conf}} file:
> {code}
> echo "layers=base,openshift" > /opt/datagrid/modules/layers.conf
> {code}
> This solution has additional advantage - we can fallback to previous KUBE_PING version (the one provided by the CE Team) by just changing this small line.
> However if the upstream KUBE_PING works fine and we are happy with it, we should remove the old version from the server. I think that's a solution we should take for JDG 8 or maybe sooner - 7.3.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months
[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] If I understood you correctly, this automatic mechanism could kick in once we receive SIGINT. WildFly already catches that and closes all subsystems. So we could do that when closing Infinispan services right?
> 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)
8 years, 5 months
[JBoss JIRA] (ISPN-8400) Adjust merge policies for JDG Online Services
by Pedro Zapata (JIRA)
[ https://issues.jboss.org/browse/ISPN-8400?page=com.atlassian.jira.plugin.... ]
Pedro Zapata updated ISPN-8400:
-------------------------------
Sprint: Sprint #4 Oct 16th - Nov 6th, Sprint #5 Nov 6th - Nov 24th 2 (was: Sprint #4 Oct 16th - Nov 6th)
> Adjust merge policies for JDG Online Services
> ---------------------------------------------
>
> Key: ISPN-8400
> URL: https://issues.jboss.org/browse/ISPN-8400
> Project: Infinispan
> Issue Type: Feature Request
> Components: Cloud Integrations
> Reporter: Sebastian Łaskawiec
> Assignee: Ryan Emerson
> Fix For: 9.2.0.Beta1
>
>
> Both Shared Memory and Caching Service require custom merge policies.
> In Caching Service we need to clear out all conflicted entries upon split brain. Shared Memory service might be a little bit more tricky and we might want to use some different strategy (but that needs to be checked out).
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 5 months