October 2019 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-10703) Operator Docs: Ability to configure resource requirements per container

by Donald Naro (Jira)

[ https://issues.jboss.org/browse/ISPN-10703?page=com.atlassian.jira.plugin... ] Donald Naro updated ISPN-10703: ------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan-operator/pull/170 > Operator Docs: Ability to configure resource requirements per container > ----------------------------------------------------------------------- > > Key: ISPN-10703 > URL: https://issues.jboss.org/browse/ISPN-10703 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation-Core > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > > Append Java options and configure CPU/memory for RHDG clusters via the Operator > https://github.com/infinispan/infinispan-operator/blob/bfa188800b4db26941... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10720) Update Caffeine to 2.8.x

by Pedro Ruivo (Jira)

[ https://issues.jboss.org/browse/ISPN-10720?page=com.atlassian.jira.plugin... ] Pedro Ruivo updated ISPN-10720: ------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Update Caffeine to 2.8.x > ------------------------ > > Key: ISPN-10720 > URL: https://issues.jboss.org/browse/ISPN-10720 > Project: Infinispan > Issue Type: Task > Components: Dependency > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 10.0.0.CR3 > > > We should update caffeine to latest version. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10704) 9.4.x: Update example hotrod-client.properties

by Donald Naro (Jira)

[ https://issues.jboss.org/browse/ISPN-10704?page=com.atlassian.jira.plugin... ] Donald Naro closed ISPN-10704. ------------------------------ > 9.4.x: Update example hotrod-client.properties > ---------------------------------------------- > > Key: ISPN-10704 > URL: https://issues.jboss.org/browse/ISPN-10704 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation-Servers > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > Fix For: 9.4.17.Final > > > https://access.redhat.com/documentation/en-us/red_hat_data_grid/7.3/html-... > Provide valid example of hotrod-client.properties. Current example is out of date. e.g. > infinispan.client.hotrod.transport_factory = org.infinispan.client.hotrod.impl.transport.tcp.TcpTransportFactory -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10704) 9.4.x: Update example hotrod-client.properties

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-10704?page=com.atlassian.jira.plugin... ] Ryan Emerson resolved ISPN-10704. --------------------------------- Fix Version/s: 9.4.17.Final Resolution: Done > 9.4.x: Update example hotrod-client.properties > ---------------------------------------------- > > Key: ISPN-10704 > URL: https://issues.jboss.org/browse/ISPN-10704 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation-Servers > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > Fix For: 9.4.17.Final > > > https://access.redhat.com/documentation/en-us/red_hat_data_grid/7.3/html-... > Provide valid example of hotrod-client.properties. Current example is out of date. e.g. > infinispan.client.hotrod.transport_factory = org.infinispan.client.hotrod.impl.transport.tcp.TcpTransportFactory -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10429) Hot Rod client doesn't retry on socket timeout

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-10429?page=com.atlassian.jira.plugin... ] Ryan Emerson resolved ISPN-10429. --------------------------------- Resolution: Done > Hot Rod client doesn't retry on socket timeout > ---------------------------------------------- > > Key: ISPN-10429 > URL: https://issues.jboss.org/browse/ISPN-10429 > Project: Infinispan > Issue Type: Bug > Components: Hot Rod > Affects Versions: 10.0.0.Beta4, 9.4.15.Final > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.0.0.CR3 > > > The Hot Rod client registers a timeout handler for operations using the socket timeout. However when this timeout is hit, the retry logic is not invoked causing requests to dead servers to fail immediately without retry. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10714) Batch support in the CLI

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-10714?page=com.atlassian.jira.plugin... ] Ryan Emerson resolved ISPN-10714. --------------------------------- Resolution: Done > Batch support in the CLI > ------------------------ > > Key: ISPN-10714 > URL: https://issues.jboss.org/browse/ISPN-10714 > Project: Infinispan > Issue Type: Enhancement > Components: CLI > Affects Versions: 10.0.0.CR2 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.0.0.CR3 > > > The CLI should support batch mode -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9966) Guidelines for evolving the API over time

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-9966?page=com.atlassian.jira.plugin.... ] Ryan Emerson updated ISPN-9966: ------------------------------- Fix Version/s: 10.0.0.CR3 > Guidelines for evolving the API over time > ----------------------------------------- > > Key: ISPN-9966 > URL: https://issues.jboss.org/browse/ISPN-9966 > Project: Infinispan > Issue Type: Sub-task > Components: API > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Major > Fix For: 10.0.0.CR3 > > > A plan on how we plan to evolve APIs over time. > * What recommendations should developers follow when they want to add/change/remove API methods? > * At which point they should come up with new interfaces and how do users migrate from one to the other? > * When should we create new modules? When can we reuse existing API modules? -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9966) Guidelines for evolving the API over time

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-9966?page=com.atlassian.jira.plugin.... ] Ryan Emerson resolved ISPN-9966. -------------------------------- Resolution: Done > Guidelines for evolving the API over time > ----------------------------------------- > > Key: ISPN-9966 > URL: https://issues.jboss.org/browse/ISPN-9966 > Project: Infinispan > Issue Type: Sub-task > Components: API > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Major > > A plan on how we plan to evolve APIs over time. > * What recommendations should developers follow when they want to add/change/remove API methods? > * At which point they should come up with new interfaces and how do users migrate from one to the other? > * When should we create new modules? When can we reuse existing API modules? -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10442) Expose XSite information via REST

by Pedro Ruivo (Jira)

[ https://issues.jboss.org/browse/ISPN-10442?page=com.atlassian.jira.plugin... ] Pedro Ruivo updated ISPN-10442: ------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 10.0.0.CR3 Resolution: Done > Expose XSite information via REST > --------------------------------- > > Key: ISPN-10442 > URL: https://issues.jboss.org/browse/ISPN-10442 > Project: Infinispan > Issue Type: Feature Request > Components: REST > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Major > Labels: console-ng > Fix For: 10.0.0.CR3 > > > Expose x-site info (status) via REST -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10618) If Expiration is enabled the cretionDate is modified to the current server start date if preload is enabled for a persistence

by Pedro Ruivo (Jira)

[ https://issues.jboss.org/browse/ISPN-10618?page=com.atlassian.jira.plugin... ] Pedro Ruivo commented on ISPN-10618: ------------------------------------ PR for 10.0 integrated! > If Expiration is enabled the cretionDate is modified to the current server start date if preload is enabled for a persistence > ----------------------------------------------------------------------------------------------------------------------------- > > Key: ISPN-10618 > URL: https://issues.jboss.org/browse/ISPN-10618 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 10.0.0.CR2 > Environment: Cache configuration with preload > <local-cache name="default"> > <persistence> > <file-store shared="false" preload="true" fetch-state="true"/> > </persistence> > </local-cache> > Reporter: Wolf-Dieter Fink > Assignee: Will Burns > Priority: Blocker > Fix For: 10.0.0.CR3, 9.4.17.Final > > > If a cache store entries with expiration the MetaData creationTime is used to calculate the expiration. > This works correct if the server is not restarted or preload=false for the store. > If preload is enabled and the server preload the date the creationTime is set to the current server start time. > In this case all expiration for existing entries is not working correctly -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 6 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 October 2019