January 2020 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-10603) Docs Productization: Partition handling

by Donald Naro (Jira)

[ https://issues.redhat.com/browse/ISPN-10603?page=com.atlassian.jira.plugi... ] Donald Naro updated ISPN-10603: ------------------------------- Sprint: DataGrid Sprint #39 > Docs Productization: Partition handling > --------------------------------------- > > Key: ISPN-10603 > URL: https://issues.redhat.com/browse/ISPN-10603 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

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

by Alan Field (Jira)

Alan Field created ISPN-11196: --------------------------------- Summary: 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: Task Components: Documentation Affects Versions: 10.1.1.Final Reporter: Alan Field 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-10836) Docs Productization: Marshalling

by Donald Naro (Jira)

[ https://issues.redhat.com/browse/ISPN-10836?page=com.atlassian.jira.plugi... ] Donald Naro updated ISPN-10836: ------------------------------- Fix Version/s: (was: 10.1.0.Final) Sprint: DataGrid Sprint #39 > Docs Productization: Marshalling > -------------------------------- > > Key: ISPN-10836 > URL: https://issues.redhat.com/browse/ISPN-10836 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > > Productize content for marshalling and protostream. > Modularize existing content. > Show consistent examples for usage (i.e. should match CLI example). > Identify additional changes and work to develop customer content. > Review Server Guide marshalling section (8. Adding Custom Marshaller Bridges) and make sure this is relevant and up to date for DG 8 > From Ryan: > - protostream and marshalling: > The important things to document are: > Jboss marshalling no longer present by default, infinispan-jboss-marshalling jar must be added to the classpath of the client/server if required. > - Externalizers ignored unless this is present > Protostream is the default marshaller for user types. Need to document the process of generating marshallers using pojos, and configuring the serialization context. > - Best practices on how to evolve schemas to ensure backwards-compatibility > Possible to configure a custom user marshaller in embedded mode, for example if the user wants to use Java Serialization but not jboss marshalling. -- 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 reopened 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, 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-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: ------------------------------- Status: Pull Request Sent (was: Reopened) > 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, 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-10583) Avoid using deprecated globalJmxStatistics().cacheManagerName()

by Nistor Adrian (Jira)

[ https://issues.redhat.com/browse/ISPN-10583?page=com.atlassian.jira.plugi... ] Nistor Adrian updated ISPN-10583: --------------------------------- Sprint: DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38 (was: DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38, DataGrid Sprint #39) > Avoid using deprecated globalJmxStatistics().cacheManagerName() > --------------------------------------------------------------- > > Key: ISPN-10583 > URL: https://issues.redhat.com/browse/ISPN-10583 > Project: Infinispan > Issue Type: Bug > Affects Versions: 10.0.0.CR1 > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 10.0.0.CR2 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10583) Avoid using deprecated globalJmxStatistics().cacheManagerName()

by Nistor Adrian (Jira)

[ https://issues.redhat.com/browse/ISPN-10583?page=com.atlassian.jira.plugi... ] Nistor Adrian closed ISPN-10583. -------------------------------- > Avoid using deprecated globalJmxStatistics().cacheManagerName() > --------------------------------------------------------------- > > Key: ISPN-10583 > URL: https://issues.redhat.com/browse/ISPN-10583 > Project: Infinispan > Issue Type: Bug > Affects Versions: 10.0.0.CR1 > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 10.0.0.CR2 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11195) InfinispanEmbeddedAutoConfiguration starts DefaultCacheManager too early

by Katia Aresti (Jira)

Katia Aresti created ISPN-11195: ----------------------------------- Summary: InfinispanEmbeddedAutoConfiguration starts DefaultCacheManager too early Key: ISPN-11195 URL: https://issues.redhat.com/browse/ISPN-11195 Project: Infinispan Issue Type: Feature Request Components: Spring Integration Reporter: Katia Aresti Details : https://github.com/infinispan/infinispan-spring-boot/issues/130 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11195) InfinispanEmbeddedAutoConfiguration starts DefaultCacheManager too early

by Katia Aresti (Jira)

[ https://issues.redhat.com/browse/ISPN-11195?page=com.atlassian.jira.plugi... ] Katia Aresti reassigned ISPN-11195: ----------------------------------- Assignee: Katia Aresti > InfinispanEmbeddedAutoConfiguration starts DefaultCacheManager too early > ------------------------------------------------------------------------ > > Key: ISPN-11195 > URL: https://issues.redhat.com/browse/ISPN-11195 > Project: Infinispan > Issue Type: Feature Request > Components: Spring Integration > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Major > > Details : https://github.com/infinispan/infinispan-spring-boot/issues/130 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10892) JBossMBeanServerLookup is deprecated and can be removed

by Nistor Adrian (Jira)

[ https://issues.redhat.com/browse/ISPN-10892?page=com.atlassian.jira.plugi... ] Nistor Adrian closed ISPN-10892. -------------------------------- > JBossMBeanServerLookup is deprecated and can be removed > ------------------------------------------------------- > > Key: ISPN-10892 > URL: https://issues.redhat.com/browse/ISPN-10892 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 10.1.0.Beta1 > > > org.jboss.mx.util.MBeanServerLocator is long gone. Some people still look for it: > https://stackoverflow.com/questions/6781376/jmx-server-locator-replacemen... -- 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