January 2020 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-11219) Docs: Capacity Factor = 0 for site masters

by Donald Naro (Jira)

[ https://issues.redhat.com/browse/ISPN-11219?page=com.atlassian.jira.plugi... ] Donald Naro updated ISPN-11219: ------------------------------- Description: Add changes from https://github.com/infinispan/infinispan/pull/7766 into 10.1 and master. (was: See here: https://infinispan.org/docs/9.4.x/user_guide/user_guide.html#capacity_fac... Using capacity factor = 0 for the site master is not a good suggestion here, since quoting [~NadirX] "in a dynamic system, where the site master is elected based on view changes, you cannot predict which node will be the master and which one needs to have its CF set to 0") > Docs: Capacity Factor = 0 for site masters > ------------------------------------------ > > Key: ISPN-11219 > URL: https://issues.redhat.com/browse/ISPN-11219 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > > Add changes from https://github.com/infinispan/infinispan/pull/7766 into 10.1 and master. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11164) Docs: Clustered max idle updates

by Donald Naro (Jira)

[ https://issues.redhat.com/browse/ISPN-11164?page=com.atlassian.jira.plugi... ] Donald Naro updated ISPN-11164: ------------------------------- Sprint: DataGrid Sprint #38 (was: DataGrid Sprint #38, DataGrid Sprint #39) > Docs: Clustered max idle updates > -------------------------------- > > Key: ISPN-11164 > URL: https://issues.redhat.com/browse/ISPN-11164 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > Fix For: 10.1.1.Final, 9.4.18.Final, 11.0.0.Final > > > whenever an entry is read that can expire via max idle, we send a touch command to all owners so they all have the same relative access time. the get won't return until the touch command has completed. > scattered the backup can be any node and we don't know which nodes are backups. in this case the touch command goes to all nodes. > if you have max idle and eviction, any access of an entry on any node will update the eviction recency on all owners as well -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11219) Docs: Capacity Factor = 0 for site masters

by Donald Naro (Jira)

[ https://issues.redhat.com/browse/ISPN-11219?page=com.atlassian.jira.plugi... ] Donald Naro updated ISPN-11219: ------------------------------- Affects Version/s: (was: 9.4.17.Final) > Docs: Capacity Factor = 0 for site masters > ------------------------------------------ > > Key: ISPN-11219 > URL: https://issues.redhat.com/browse/ISPN-11219 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Blocker > Fix For: 9.4.18.Final > > > See here: https://infinispan.org/docs/9.4.x/user_guide/user_guide.html#capacity_fac... > Using capacity factor = 0 for the site master is not a good suggestion here, since quoting [~NadirX] "in a dynamic system, where the site master is elected based on view changes, you cannot predict which node will be the master and which one needs to have its CF set to 0" -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11196) Docs: Remove suggestion about using Capacity Factor = 0 for site masters

by Donald Naro (Jira)

[ https://issues.redhat.com/browse/ISPN-11196?page=com.atlassian.jira.plugi... ] Donald Naro closed ISPN-11196. ------------------------------ > Docs: Remove suggestion about using Capacity Factor = 0 for site masters > ------------------------------------------------------------------------ > > Key: ISPN-11196 > URL: https://issues.redhat.com/browse/ISPN-11196 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation > Affects Versions: 9.4.17.Final > Reporter: Alan Field > Assignee: Donald Naro > Priority: Blocker > Fix For: 9.4.18.Final > > > See here: https://infinispan.org/docs/9.4.x/user_guide/user_guide.html#capacity_fac... > Using capacity factor = 0 for the site master is not a good suggestion here, since quoting [~NadirX] "in a dynamic system, where the site master is elected based on view changes, you cannot predict which node will be the master and which one needs to have its CF set to 0" -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11219) Docs: Capacity Factor = 0 for site masters

by Donald Naro (Jira)

[ https://issues.redhat.com/browse/ISPN-11219?page=com.atlassian.jira.plugi... ] Donald Naro updated ISPN-11219: ------------------------------- Priority: Major (was: Blocker) > Docs: Capacity Factor = 0 for site masters > ------------------------------------------ > > Key: ISPN-11219 > URL: https://issues.redhat.com/browse/ISPN-11219 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > Fix For: 9.4.18.Final > > > See here: https://infinispan.org/docs/9.4.x/user_guide/user_guide.html#capacity_fac... > Using capacity factor = 0 for the site master is not a good suggestion here, since quoting [~NadirX] "in a dynamic system, where the site master is elected based on view changes, you cannot predict which node will be the master and which one needs to have its CF set to 0" -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11196) Docs: Remove suggestion about using Capacity Factor = 0 for site masters

by Donald Naro (Jira)

[ https://issues.redhat.com/browse/ISPN-11196?page=com.atlassian.jira.plugi... ] Donald Naro updated ISPN-11196: ------------------------------- Sprint: (was: DataGrid Sprint #39) > Docs: Remove suggestion about using Capacity Factor = 0 for site masters > ------------------------------------------------------------------------ > > Key: ISPN-11196 > URL: https://issues.redhat.com/browse/ISPN-11196 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation > Affects Versions: 9.4.17.Final > Reporter: Alan Field > Assignee: Donald Naro > Priority: Blocker > Fix For: 9.4.18.Final > > > See here: https://infinispan.org/docs/9.4.x/user_guide/user_guide.html#capacity_fac... > Using capacity factor = 0 for the site master is not a good suggestion here, since quoting [~NadirX] "in a dynamic system, where the site master is elected based on view changes, you cannot predict which node will be the master and which one needs to have its CF set to 0" -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11164) Docs: Clustered max idle updates

by Donald Naro (Jira)

[ https://issues.redhat.com/browse/ISPN-11164?page=com.atlassian.jira.plugi... ] Donald Naro closed ISPN-11164. ------------------------------ > Docs: Clustered max idle updates > -------------------------------- > > Key: ISPN-11164 > URL: https://issues.redhat.com/browse/ISPN-11164 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > Fix For: 10.1.1.Final, 9.4.18.Final, 11.0.0.Final > > > whenever an entry is read that can expire via max idle, we send a touch command to all owners so they all have the same relative access time. the get won't return until the touch command has completed. > scattered the backup can be any node and we don't know which nodes are backups. in this case the touch command goes to all nodes. > if you have max idle and eviction, any access of an entry on any node will update the eviction recency on all owners as well -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11219) Docs: Capacity Factor = 0 for site masters

by Donald Naro (Jira)

Donald Naro created ISPN-11219: ---------------------------------- Summary: Docs: Capacity Factor = 0 for site masters Key: ISPN-11219 URL: https://issues.redhat.com/browse/ISPN-11219 Project: Infinispan Issue Type: Enhancement Components: Documentation Affects Versions: 9.4.17.Final Reporter: Donald Naro Assignee: Donald Naro Fix For: 9.4.18.Final See here: https://infinispan.org/docs/9.4.x/user_guide/user_guide.html#capacity_fac... Using capacity factor = 0 for the site master is not a good suggestion here, since quoting [~NadirX] "in a dynamic system, where the site master is elected based on view changes, you cannot predict which node will be the master and which one needs to have its CF set to 0" -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11196) Docs: Remove suggestion about using Capacity Factor = 0 for site masters

by Dan Berindei (Jira)

[ https://issues.redhat.com/browse/ISPN-11196?page=com.atlassian.jira.plugi... ] Dan Berindei updated ISPN-11196: -------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.4.18.Final Resolution: Done > Docs: Remove suggestion about using Capacity Factor = 0 for site masters > ------------------------------------------------------------------------ > > Key: ISPN-11196 > URL: https://issues.redhat.com/browse/ISPN-11196 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation > Affects Versions: 9.4.17.Final > Reporter: Alan Field > Assignee: Donald Naro > Priority: Blocker > Fix For: 9.4.18.Final > > > See here: https://infinispan.org/docs/9.4.x/user_guide/user_guide.html#capacity_fac... > Using capacity factor = 0 for the site master is not a good suggestion here, since quoting [~NadirX] "in a dynamic system, where the site master is elected based on view changes, you cannot predict which node will be the master and which one needs to have its CF set to 0" -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11164) Docs: Clustered max idle updates

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-11164?page=com.atlassian.jira.plugi... ] Will Burns updated ISPN-11164: ------------------------------ Fix Version/s: 9.4.18.Final > Docs: Clustered max idle updates > -------------------------------- > > Key: ISPN-11164 > URL: https://issues.redhat.com/browse/ISPN-11164 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > Fix For: 10.1.1.Final, 9.4.18.Final, 11.0.0.Final > > > whenever an entry is read that can expire via max idle, we send a touch command to all owners so they all have the same relative access time. the get won't return until the touch command has completed. > scattered the backup can be any node and we don't know which nodes are backups. in this case the touch command goes to all nodes. > if you have max idle and eviction, any access of an entry on any node will update the eviction recency on all owners as well -- 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