November 2018 - infinispan-issues

[JBoss JIRA] (ISPN-9699) Cluster member owning no data

by Katia Aresti (Jira)

[ https://issues.jboss.org/browse/ISPN-9699?page=com.atlassian.jira.plugin.... ] Katia Aresti updated ISPN-9699: ------------------------------- Status: Open (was: New) > Cluster member owning no data > ----------------------------- > > Key: ISPN-9699 > URL: https://issues.jboss.org/browse/ISPN-9699 > Project: Infinispan > Issue Type: Feature Request > Affects Versions: 9.4.1.Final > Reporter: Thomas Segismont > Assignee: Katia Aresti > Priority: Major > Fix For: 10.0.0.Alpha2, 9.4.3.Final > > > Currently, you can set {{capacity-factor}} to zero on a cache if you don't want a node to own any segment. > If you want a node to own no data at all, you could set this property on all declared cached. But this wouldn't work for internal caches anyway (locks, counters). > It would be nice to have a global switch. > This would be useful when your app needs to be a cluster member for discovery/membership but is deployed mostly for processing. Indeed, when such nodes are added/removed from the cluster: > * there would be no data loss > * the cluster would be back in healthy state faster as no data would be moved around. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9699) Cluster member owning no data

by Katia Aresti (Jira)

[ https://issues.jboss.org/browse/ISPN-9699?page=com.atlassian.jira.plugin.... ] Katia Aresti updated ISPN-9699: ------------------------------- Fix Version/s: 9.4.3.Final 10.0.0.Alpha2 > Cluster member owning no data > ----------------------------- > > Key: ISPN-9699 > URL: https://issues.jboss.org/browse/ISPN-9699 > Project: Infinispan > Issue Type: Feature Request > Components: Core > Affects Versions: 9.4.1.Final > Reporter: Thomas Segismont > Assignee: Katia Aresti > Priority: Major > Fix For: 10.0.0.Alpha2, 9.4.3.Final > > > Currently, you can set {{capacity-factor}} to zero on a cache if you don't want a node to own any segment. > If you want a node to own no data at all, you could set this property on all declared cached. But this wouldn't work for internal caches anyway (locks, counters). > It would be nice to have a global switch. > This would be useful when your app needs to be a cluster member for discovery/membership but is deployed mostly for processing. Indeed, when such nodes are added/removed from the cluster: > * there would be no data loss > * the cluster would be back in healthy state faster as no data would be moved around. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9699) Cluster member owning no data

by Katia Aresti (Jira)

[ https://issues.jboss.org/browse/ISPN-9699?page=com.atlassian.jira.plugin.... ] Katia Aresti updated ISPN-9699: ------------------------------- Affects Version/s: 9.4.1.Final > Cluster member owning no data > ----------------------------- > > Key: ISPN-9699 > URL: https://issues.jboss.org/browse/ISPN-9699 > Project: Infinispan > Issue Type: Feature Request > Components: Core > Affects Versions: 9.4.1.Final > Reporter: Thomas Segismont > Assignee: Katia Aresti > Priority: Major > Fix For: 10.0.0.Alpha2, 9.4.3.Final > > > Currently, you can set {{capacity-factor}} to zero on a cache if you don't want a node to own any segment. > If you want a node to own no data at all, you could set this property on all declared cached. But this wouldn't work for internal caches anyway (locks, counters). > It would be nice to have a global switch. > This would be useful when your app needs to be a cluster member for discovery/membership but is deployed mostly for processing. Indeed, when such nodes are added/removed from the cluster: > * there would be no data loss > * the cluster would be back in healthy state faster as no data would be moved around. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9699) Cluster member owning no data

by Katia Aresti (Jira)

[ https://issues.jboss.org/browse/ISPN-9699?page=com.atlassian.jira.plugin.... ] Katia Aresti updated ISPN-9699: ------------------------------- Component/s: Core > Cluster member owning no data > ----------------------------- > > Key: ISPN-9699 > URL: https://issues.jboss.org/browse/ISPN-9699 > Project: Infinispan > Issue Type: Feature Request > Components: Core > Affects Versions: 9.4.1.Final > Reporter: Thomas Segismont > Assignee: Katia Aresti > Priority: Major > Fix For: 10.0.0.Alpha2, 9.4.3.Final > > > Currently, you can set {{capacity-factor}} to zero on a cache if you don't want a node to own any segment. > If you want a node to own no data at all, you could set this property on all declared cached. But this wouldn't work for internal caches anyway (locks, counters). > It would be nice to have a global switch. > This would be useful when your app needs to be a cluster member for discovery/membership but is deployed mostly for processing. Indeed, when such nodes are added/removed from the cluster: > * there would be no data loss > * the cluster would be back in healthy state faster as no data would be moved around. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9703) CI should test that distribution build works

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-9703?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-9703: ------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/6439 (was: https://github.com/infinispan/infinispan/pull/6388) > CI should test that distribution build works > -------------------------------------------- > > Key: ISPN-9703 > URL: https://issues.jboss.org/browse/ISPN-9703 > Project: Infinispan > Issue Type: Enhancement > Affects Versions: 9.4.1.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.0.Alpha1 > > > Currently the CI does not test whether the `-Pdistribution` profile successfully builds or not. As we want master to always be releasable, we should test this on PRs. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9741) Docs: Formatting Issues in Server Guide

by Don Naro (Jira)

[ https://issues.jboss.org/browse/ISPN-9741?page=com.atlassian.jira.plugin.... ] Don Naro updated ISPN-9741: --------------------------- Affects Version/s: 9.4.1.Final 10.0.0.Alpha1 (was: 10.0.0.Alpha2) (was: 9.4.2.Final) > Docs: Formatting Issues in Server Guide > --------------------------------------- > > Key: ISPN-9741 > URL: https://issues.jboss.org/browse/ISPN-9741 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation-Servers > Affects Versions: 9.4.1.Final, 10.0.0.Alpha1 > Reporter: Don Naro > Assignee: Don Naro > Priority: Major > > Formatting error at the end of the section, == Security should have been the start of the next chapter -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9741) Docs: Formatting Issues in Server Guide

by Don Naro (Jira)

[ https://issues.jboss.org/browse/ISPN-9741?page=com.atlassian.jira.plugin.... ] Don Naro updated ISPN-9741: --------------------------- Affects Version/s: 9.4.2.Final 10.0.0.Alpha2 > Docs: Formatting Issues in Server Guide > --------------------------------------- > > Key: ISPN-9741 > URL: https://issues.jboss.org/browse/ISPN-9741 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation-Servers > Affects Versions: 9.4.2.Final, 10.0.0.Alpha2 > Reporter: Don Naro > Assignee: Don Naro > Priority: Major > > Formatting error at the end of the section, == Security should have been the start of the next chapter -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9741) Docs: Formatting Issues in Server Guide

by Don Naro (Jira)

[ https://issues.jboss.org/browse/ISPN-9741?page=com.atlassian.jira.plugin.... ] Don Naro updated ISPN-9741: --------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/6432 > Docs: Formatting Issues in Server Guide > --------------------------------------- > > Key: ISPN-9741 > URL: https://issues.jboss.org/browse/ISPN-9741 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation-Servers > Reporter: Don Naro > Assignee: Don Naro > Priority: Major > > Formatting error at the end of the section, == Security should have been the start of the next chapter -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9741) Docs: Formatting Issues in Server Guide

by Don Naro (Jira)

[ https://issues.jboss.org/browse/ISPN-9741?page=com.atlassian.jira.plugin.... ] Don Naro updated ISPN-9741: --------------------------- Status: Open (was: New) > Docs: Formatting Issues in Server Guide > --------------------------------------- > > Key: ISPN-9741 > URL: https://issues.jboss.org/browse/ISPN-9741 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation-Servers > Reporter: Don Naro > Assignee: Don Naro > Priority: Major > > Formatting error at the end of the section, == Security should have been the start of the next chapter -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9747) Backport branding changes for Cassandra CacheStore

by Pedro Ruivo (Jira)

[ https://issues.jboss.org/browse/ISPN-9747?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-9747: ------------------------------ Status: Open (was: New) > Backport branding changes for Cassandra CacheStore > -------------------------------------------------- > > Key: ISPN-9747 > URL: https://issues.jboss.org/browse/ISPN-9747 > Project: Infinispan > Issue Type: Enhancement > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues November 2018