November 2019 - infinispan-issues

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

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10429?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10429: ----------------------------------- Fix Version/s: 9.4.17.Final > 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, 9.4.17.Final > > > 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, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10734) Operator Docs: Auto scale on memory usage

by Donald Naro (Jira)

[ https://issues.jboss.org/browse/ISPN-10734?page=com.atlassian.jira.plugin... ] Donald Naro updated ISPN-10734: ------------------------------- Sprint: DataGrid Sprint #37 (was: DataGrid Sprint #36) > Operator Docs: Auto scale on memory usage > ----------------------------------------- > > Key: ISPN-10734 > URL: https://issues.jboss.org/browse/ISPN-10734 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation-Servers > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > > https://github.com/infinispan/infinispan-operator/issues/160 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10945) MassIndexer flushes indexes asynchronously even when running in sync mode

by Gustavo Fernandes (Jira)

[ https://issues.jboss.org/browse/ISPN-10945?page=com.atlassian.jira.plugin... ] Gustavo Fernandes commented on ISPN-10945: ------------------------------------------ This was introduced by a wrong change at https://github.com/infinispan/infinispan/pull/7051 > MassIndexer flushes indexes asynchronously even when running in sync mode > ------------------------------------------------------------------------- > > Key: ISPN-10945 > URL: https://issues.jboss.org/browse/ISPN-10945 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Affects Versions: 10.0.0.Final > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10945) MassIndexer flushes indexes asynchronously even when running in sync mode

by Gustavo Fernandes (Jira)

Gustavo Fernandes created ISPN-10945: ---------------------------------------- Summary: MassIndexer flushes indexes asynchronously even when running in sync mode Key: ISPN-10945 URL: https://issues.jboss.org/browse/ISPN-10945 Project: Infinispan Issue Type: Bug Components: Embedded Querying Affects Versions: 10.0.0.Final Reporter: Gustavo Fernandes Assignee: Gustavo Fernandes -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

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

by Tristan Tarrant (Jira)

Tristan Tarrant created ISPN-10944: -------------------------------------- Summary: Hot Rod client doesn't retry on socket timeout Key: ISPN-10944 URL: https://issues.jboss.org/browse/ISPN-10944 Project: Infinispan Issue Type: Bug Components: Hot Rod Affects Versions: 10.0.0.Beta4, 9.4.15.Final Reporter: Tristan Tarrant Assignee: Tristan Tarrant 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, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8115) Remove Index.LOCAL

by Nistor Adrian (Jira)

[ https://issues.jboss.org/browse/ISPN-8115?page=com.atlassian.jira.plugin.... ] Nistor Adrian commented on ISPN-8115: ------------------------------------- The last standing deprecated bits of 'remove index local' where removed as part of ISPN-8357 > Remove Index.LOCAL > ------------------ > > Key: ISPN-8115 > URL: https://issues.jboss.org/browse/ISPN-8115 > Project: Infinispan > Issue Type: Sub-task > Components: Embedded Querying > Affects Versions: 9.1.0.Final > Reporter: Radim Vansa > Assignee: Gustavo Fernandes > Priority: Major > Fix For: 10.1.0.Final > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8115) Remove Index.LOCAL

by Gustavo Fernandes (Jira)

[ https://issues.jboss.org/browse/ISPN-8115?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes resolved ISPN-8115. ------------------------------------- Resolution: Out of Date > Remove Index.LOCAL > ------------------ > > Key: ISPN-8115 > URL: https://issues.jboss.org/browse/ISPN-8115 > Project: Infinispan > Issue Type: Sub-task > Components: Embedded Querying > Affects Versions: 9.1.0.Final > Reporter: Radim Vansa > Assignee: Gustavo Fernandes > Priority: Major > Fix For: 10.1.0.Final > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10883) [REST] Simultaneous call to stop don't stop the servers

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10883?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10883: ----------------------------------- Status: Open (was: New) > [REST] Simultaneous call to stop don't stop the servers > ------------------------------------------------------- > > Key: ISPN-10883 > URL: https://issues.jboss.org/browse/ISPN-10883 > Project: Infinispan > Issue Type: Bug > Components: REST, Server > Affects Versions: 10.0.0.Final, 10.0.1.Final > Reporter: Gustavo Fernandes > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.1.0.Beta1 > > > This was observed in a cluster of 3 servers in the same machine, listening on ports 11222, 11322, 11422. A script would call stop on each of the server individually: > http://localhost:11222/rest/v2/server?action=stop > http://localhost:11322/rest/v2/server?action=stop > http://localhost:11422/rest/v2/server?action=stop > All the commands return code 200 but the servers are not stopped, the processes are still alive. > This is a regression from 10.0.0.CR3 where those ops were working correctly. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10883) [REST] Simultaneous call to stop don't stop the servers

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10883?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10883: ----------------------------------- Fix Version/s: 10.1.0.Beta1 > [REST] Simultaneous call to stop don't stop the servers > ------------------------------------------------------- > > Key: ISPN-10883 > URL: https://issues.jboss.org/browse/ISPN-10883 > Project: Infinispan > Issue Type: Bug > Components: REST, Server > Affects Versions: 10.0.0.Final, 10.0.1.Final > Reporter: Gustavo Fernandes > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.1.0.Beta1 > > > This was observed in a cluster of 3 servers in the same machine, listening on ports 11222, 11322, 11422. A script would call stop on each of the server individually: > http://localhost:11222/rest/v2/server?action=stop > http://localhost:11322/rest/v2/server?action=stop > http://localhost:11422/rest/v2/server?action=stop > All the commands return code 200 but the servers are not stopped, the processes are still alive. > This is a regression from 10.0.0.CR3 where those ops were working correctly. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10883) [REST] Simultaneous call to stop don't stop the servers

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10883?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10883: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/7585 > [REST] Simultaneous call to stop don't stop the servers > ------------------------------------------------------- > > Key: ISPN-10883 > URL: https://issues.jboss.org/browse/ISPN-10883 > Project: Infinispan > Issue Type: Bug > Components: REST, Server > Affects Versions: 10.0.0.Final, 10.0.1.Final > Reporter: Gustavo Fernandes > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.1.0.Beta1 > > > This was observed in a cluster of 3 servers in the same machine, listening on ports 11222, 11322, 11422. A script would call stop on each of the server individually: > http://localhost:11222/rest/v2/server?action=stop > http://localhost:11322/rest/v2/server?action=stop > http://localhost:11422/rest/v2/server?action=stop > All the commands return code 200 but the servers are not stopped, the processes are still alive. > This is a regression from 10.0.0.CR3 where those ops were working correctly. -- This message was sent by Atlassian Jira (v7.13.8#713008)

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