April 2020 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-11710) MassIndexer timeouts after 4 minutes

by Gustavo Fernandes (Jira)

[ https://issues.redhat.com/browse/ISPN-11710?page=com.atlassian.jira.plugi... ] Gustavo Fernandes updated ISPN-11710: ------------------------------------- Description: The MassIndexer on a clustered cache follows the Transport timeout configuration that is 4 minutes by default. On Local caches, it always uses 4 minutes (hardcoded). Until it is possible to cancel the MassIndexer (see ISPN-11735), it should not timeout. was: The MassIndexer on a clustered cache follows the Transport timeout configuration that is 4 minutes by default. On Local caches, it always uses 4 minutes (hardcoded). Until it is possible to cancel the MassIndexer (see ISPN-11735) > MassIndexer timeouts after 4 minutes > ------------------------------------ > > Key: ISPN-11710 > URL: https://issues.redhat.com/browse/ISPN-11710 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying > Affects Versions: 11.0.0.Dev04, 10.1.6.Final > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Major > > The MassIndexer on a clustered cache follows the Transport timeout configuration that is 4 minutes by default. On Local caches, it always uses 4 minutes (hardcoded). > Until it is possible to cancel the MassIndexer (see ISPN-11735), it should not timeout. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11735) Supporting cancellation in the ClusterExecutor

by Gustavo Fernandes (Jira)

Gustavo Fernandes created ISPN-11735: ---------------------------------------- Summary: Supporting cancellation in the ClusterExecutor Key: ISPN-11735 URL: https://issues.redhat.com/browse/ISPN-11735 Project: Infinispan Issue Type: Enhancement Components: Core Affects Versions: 11.0.0.Dev04 Reporter: Gustavo Fernandes Assignee: Will Burns Currently the ClusterExecutor can timeout and leave commands running in the server, without the possibility of signalling a cancel to them. One idea is to implement the cancellation logic in the {{CompletableFuture.cancel(boolean ignored)}} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11710) MassIndexer timeouts after 4 minutes

by Gustavo Fernandes (Jira)

[ https://issues.redhat.com/browse/ISPN-11710?page=com.atlassian.jira.plugi... ] Gustavo Fernandes updated ISPN-11710: ------------------------------------- Description: The MassIndexer on a clustered cache follows the Transport timeout configuration that is 4 minutes by default. On Local caches, it always uses 4 minutes (hardcoded). Until it is possible to cancel the MassIndexer (see ISPN-11735) was: The MassIndexer on a clustered cache follows the Transport timeout configuration that is 4 minutes by default. On Local caches, it always uses 4 minutes (hardcoded). Until it is possible to cancel the MassI > MassIndexer timeouts after 4 minutes > ------------------------------------ > > Key: ISPN-11710 > URL: https://issues.redhat.com/browse/ISPN-11710 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying > Affects Versions: 11.0.0.Dev04, 10.1.6.Final > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Major > > The MassIndexer on a clustered cache follows the Transport timeout configuration that is 4 minutes by default. On Local caches, it always uses 4 minutes (hardcoded). > Until it is possible to cancel the MassIndexer (see ISPN-11735) -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11710) MassIndexer timeouts after 4 minutes

by Gustavo Fernandes (Jira)

[ https://issues.redhat.com/browse/ISPN-11710?page=com.atlassian.jira.plugi... ] Gustavo Fernandes updated ISPN-11710: ------------------------------------- Description: The MassIndexer on a clustered cache follows the Transport timeout configuration that is 4 minutes by default. On Local caches, it always uses 4 minutes (hardcoded). Until it is possible to cancel the MassI > MassIndexer timeouts after 4 minutes > ------------------------------------ > > Key: ISPN-11710 > URL: https://issues.redhat.com/browse/ISPN-11710 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying > Affects Versions: 11.0.0.Dev04, 10.1.6.Final > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Major > > The MassIndexer on a clustered cache follows the Transport timeout configuration that is 4 minutes by default. On Local caches, it always uses 4 minutes (hardcoded). > Until it is possible to cancel the MassI -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11710) MassIndexer timeouts after 4 minutes

by Gustavo Fernandes (Jira)

[ https://issues.redhat.com/browse/ISPN-11710?page=com.atlassian.jira.plugi... ] Gustavo Fernandes updated ISPN-11710: ------------------------------------- Summary: MassIndexer timeouts after 4 minutes (was: Make the MassIndexer timeout configurable) > MassIndexer timeouts after 4 minutes > ------------------------------------ > > Key: ISPN-11710 > URL: https://issues.redhat.com/browse/ISPN-11710 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying > Affects Versions: 11.0.0.Dev04, 10.1.6.Final > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11202) Infinispan BOM is missing an entry for 'infinispan-jcache-commons'

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11202?page=com.atlassian.jira.plugi... ] Tristan Tarrant commented on ISPN-11202: ---------------------------------------- I've read the description and it is not clear. It is a dependency management problem ONLY if you explicitly depend on infinispan-jcache-commons. > Infinispan BOM is missing an entry for 'infinispan-jcache-commons' > ------------------------------------------------------------------ > > Key: ISPN-11202 > URL: https://issues.redhat.com/browse/ISPN-11202 > Project: Infinispan > Issue Type: Bug > Components: Build > Affects Versions: 10.1.1.Final > Reporter: Stéphane Nicoll > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.1.7.Final, 11.0.0.Dev05 > > > The BOM currently misses an entry for {{infinispan-jcache-commons}} so there is a chance for that module to get out-of-sync even if the bom is used. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11734) Store endpoint topology info for all protocols

by Tristan Tarrant (Jira)

Tristan Tarrant created ISPN-11734: -------------------------------------- Summary: Store endpoint topology info for all protocols Key: ISPN-11734 URL: https://issues.redhat.com/browse/ISPN-11734 Project: Infinispan Issue Type: Enhancement Components: Remote Protocols, Server Reporter: Tristan Tarrant Currently, only the Hot Rod server holds a topology cache containing the public addresses of the endpoint. This code should be moved to the core protocol server so it can be shared by all protocols. This would enable retrieving all of the addresses of the other protocols (i.e. REST) to aid with intelligent clients -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11734) Store endpoint topology info for all protocols

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11734?page=com.atlassian.jira.plugi... ] Tristan Tarrant reassigned ISPN-11734: -------------------------------------- Assignee: Tristan Tarrant > Store endpoint topology info for all protocols > ---------------------------------------------- > > Key: ISPN-11734 > URL: https://issues.redhat.com/browse/ISPN-11734 > Project: Infinispan > Issue Type: Enhancement > Components: Remote Protocols, Server > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > > Currently, only the Hot Rod server holds a topology cache containing the public addresses of the endpoint. > This code should be moved to the core protocol server so it can be shared by all protocols. > This would enable retrieving all of the addresses of the other protocols (i.e. REST) to aid with intelligent clients -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11202) Infinispan BOM is missing an entry for 'infinispan-jcache-commons'

by Stéphane Nicoll (Jira)

[ https://issues.redhat.com/browse/ISPN-11202?page=com.atlassian.jira.plugi... ] Stéphane Nicoll commented on ISPN-11202: ---------------------------------------- This issue is about dependency management, not what users would do in their projects. Please see the description of the issue and let me know if something isn't clear. > Infinispan BOM is missing an entry for 'infinispan-jcache-commons' > ------------------------------------------------------------------ > > Key: ISPN-11202 > URL: https://issues.redhat.com/browse/ISPN-11202 > Project: Infinispan > Issue Type: Bug > Components: Build > Affects Versions: 10.1.1.Final > Reporter: Stéphane Nicoll > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.1.7.Final, 11.0.0.Dev05 > > > The BOM currently misses an entry for {{infinispan-jcache-commons}} so there is a chance for that module to get out-of-sync even if the bom is used. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11202) Infinispan BOM is missing an entry for 'infinispan-jcache-commons'

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11202?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11202: ----------------------------------- Status: Open (was: New) > Infinispan BOM is missing an entry for 'infinispan-jcache-commons' > ------------------------------------------------------------------ > > Key: ISPN-11202 > URL: https://issues.redhat.com/browse/ISPN-11202 > Project: Infinispan > Issue Type: Bug > Components: Build > Affects Versions: 10.1.1.Final > Reporter: Stéphane Nicoll > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.1.7.Final, 11.0.0.Dev05 > > > The BOM currently misses an entry for {{infinispan-jcache-commons}} so there is a chance for that module to get out-of-sync even if the bom is used. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues April 2020