March 2020 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-11435) The server sometimes doesn't start all the caches

by Pedro Zapata Fernandez (Jira)

[ https://issues.redhat.com/browse/ISPN-11435?page=com.atlassian.jira.plugi... ] Pedro Zapata Fernandez updated ISPN-11435: ------------------------------------------ Priority: Critical (was: Major) > The server sometimes doesn't start all the caches > ------------------------------------------------- > > Key: ISPN-11435 > URL: https://issues.redhat.com/browse/ISPN-11435 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 10.1.3.Final, 11.0.0.Alpha2 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Critical > Fix For: 10.1.4.Final, 11.0.0.Dev03 > > > Our regression tests are reporting throughput variations between builds with no significant differences, and we tracked it down to some servers not starting all the caches. > {{HotRodServer}} is currently responsible for starting all the defined caches in the {{preStartCaches()}} method. We might want to move this functionality to the generic server or to {{DefaultCacheManager}} itself. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-10012) Observability: Qualify metrics using Prometheus naming

by Nistor Adrian (Jira)

[ https://issues.redhat.com/browse/ISPN-10012?page=com.atlassian.jira.plugi... ] Nistor Adrian closed ISPN-10012. -------------------------------- Fix Version/s: 11.0.0.Alpha2 10.1.3.Final Resolution: Done Closing this as the fix was already included in the PR for ISPN-11174 > Observability: Qualify metrics using Prometheus naming > ------------------------------------------------------ > > Key: ISPN-10012 > URL: https://issues.redhat.com/browse/ISPN-10012 > Project: Infinispan > Issue Type: Sub-task > Components: JMX, reporting and management > Reporter: Tristan Tarrant > Assignee: Nistor Adrian > Priority: Major > Fix For: 11.0.0.Alpha2, 10.1.3.Final > > > We currently annotate metrics using conventions derived from RHQ. We should update the convention to that used by Prometheus (Counters, Gauges, etc) -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-10012) Observability: Qualify metrics using Prometheus naming

by Nistor Adrian (Jira)

[ https://issues.redhat.com/browse/ISPN-10012?page=com.atlassian.jira.plugi... ] Nistor Adrian commented on ISPN-10012: -------------------------------------- [~NadirX] The metrics are currently using snake case naming. All parts of the name are lowercased. Except the included cache manager name and cache name, which are left as they are, no lowercasing, no snake casing. But non-complying characters are still replaced with '_'. I believe this is pretty much what Prometheus conventions are. The actual metric name is formed like: `cache_manager_MyCacheManager_cache_MyCache_statistics_stores` by default. An additional `prefix` attribute in the <metrics> element allow us to specify a prefix, just in case we need to avoid some conflict. Default prefix is empty. The boolean attribute `namesAsTags` allows us to switch to using fixed metric names, that do not contain variable parts like the cache manager name / cache name. Instead these are added as tags when namesAsTags=true. So the metric name would be simply `statistics_stores` with tags [cache_manager="MyCacheManager", cache="MyCache"] > Observability: Qualify metrics using Prometheus naming > ------------------------------------------------------ > > Key: ISPN-10012 > URL: https://issues.redhat.com/browse/ISPN-10012 > Project: Infinispan > Issue Type: Sub-task > Components: JMX, reporting and management > Reporter: Tristan Tarrant > Assignee: Nistor Adrian > Priority: Major > Fix For: 10.1.3.Final, 11.0.0.Alpha2 > > > We currently annotate metrics using conventions derived from RHQ. We should update the convention to that used by Prometheus (Counters, Gauges, etc) -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-11126) Health check fails when authz is enabled and cache is not yet started

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11126?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11126: ----------------------------------- Fix Version/s: 11.0.0.Dev03 > Health check fails when authz is enabled and cache is not yet started > --------------------------------------------------------------------- > > Key: ISPN-11126 > URL: https://issues.redhat.com/browse/ISPN-11126 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management, REST > Affects Versions: 10.1.0.Final > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.1.4.Final, 11.0.0.Dev03 > > > When using predefined caches on a container with authorization, and the caches have not been started, the health handler for the cachemanager resource fails with an authorization error. > The call should be wrapped in a SecurityAction. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-11126) Health check fails when authz is enabled and cache is not yet started

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11126?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11126: ----------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/8017 (was: https://github.com/infinispan/infinispan/pull/7716) > Health check fails when authz is enabled and cache is not yet started > --------------------------------------------------------------------- > > Key: ISPN-11126 > URL: https://issues.redhat.com/browse/ISPN-11126 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management, REST > Affects Versions: 10.1.0.Final > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.1.4.Final, 11.0.0.Dev03 > > > When using predefined caches on a container with authorization, and the caches have not been started, the health handler for the cachemanager resource fails with an authorization error. > The call should be wrapped in a SecurityAction. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-11440) Allow use of config sub-elements in XIncluded fragments

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11440?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11440: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/8016 > Allow use of config sub-elements in XIncluded fragments > ------------------------------------------------------- > > Key: ISPN-11440 > URL: https://issues.redhat.com/browse/ISPN-11440 > Project: Infinispan > Issue Type: Enhancement > Components: Configuration > Affects Versions: 11.0.0.Alpha2 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 11.0.0.Dev03 > > > The infinispan-config XSD only allows the {{infinispan}} element as a top-level element. However, when using XInclude, it would be useful to be able to have other kinds of top-level elements: > jgroups > threads > cache-container > transport > security > *-cache-* -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-11440) Allow use of config sub-elements in XIncluded fragments

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11440?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11440: ----------------------------------- Status: Open (was: New) > Allow use of config sub-elements in XIncluded fragments > ------------------------------------------------------- > > Key: ISPN-11440 > URL: https://issues.redhat.com/browse/ISPN-11440 > Project: Infinispan > Issue Type: Enhancement > Components: Configuration > Affects Versions: 11.0.0.Alpha2 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 11.0.0.Dev03 > > > The infinispan-config XSD only allows the {{infinispan}} element as a top-level element. However, when using XInclude, it would be useful to be able to have other kinds of top-level elements: > jgroups > threads > cache-container > transport > security > *-cache-* -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-11435) The server sometimes doesn't start all the caches

by Dan Berindei (Jira)

[ https://issues.redhat.com/browse/ISPN-11435?page=com.atlassian.jira.plugi... ] Dan Berindei commented on ISPN-11435: ------------------------------------- {{HotRodServer.startTransport}} is not called in single port configurations, and because of that the server doesn't pre-start all the caches defined in the XML configuration. Defined caches will be started if a client accesses this server when it first connects, but later requests will go to the servers that already have the cache running. > The server sometimes doesn't start all the caches > ------------------------------------------------- > > Key: ISPN-11435 > URL: https://issues.redhat.com/browse/ISPN-11435 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 10.1.3.Final, 11.0.0.Alpha2 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 10.1.4.Final, 11.0.0.Dev03 > > > Our regression tests are reporting throughput variations between builds with no significant differences, and we tracked it down to some servers not starting all the caches. > {{HotRodServer}} is currently responsible for starting all the defined caches in the {{preStartCaches()}} method. We might want to move this functionality to the generic server or to {{DefaultCacheManager}} itself. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-11440) Allow use of config sub-elements in XIncluded fragments

by Tristan Tarrant (Jira)

Tristan Tarrant created ISPN-11440: -------------------------------------- Summary: Allow use of config sub-elements in XIncluded fragments Key: ISPN-11440 URL: https://issues.redhat.com/browse/ISPN-11440 Project: Infinispan Issue Type: Enhancement Components: Configuration Affects Versions: 11.0.0.Alpha2 Reporter: Tristan Tarrant Assignee: Tristan Tarrant Fix For: 11.0.0.Dev03 The infinispan-config XSD only allows the {{infinispan}} element as a top-level element. However, when using XInclude, it would be useful to be able to have other kinds of top-level elements: jgroups threads cache-container transport security *-cache-* -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-11439) The server sometimes doesn't start all the caches

by Diego Lovison (Jira)

Diego Lovison created ISPN-11439: ------------------------------------ Summary: The server sometimes doesn't start all the caches Key: ISPN-11439 URL: https://issues.redhat.com/browse/ISPN-11439 Project: Infinispan Issue Type: Bug Components: Server Affects Versions: 10.1.3.Final, 11.0.0.Alpha2 Reporter: Diego Lovison Assignee: Dan Berindei Fix For: 10.1.4.Final, 11.0.0.Dev03 Our regression tests are reporting throughput variations between builds with no significant differences, and we tracked it down to some servers not starting all the caches. {{HotRodServer}} is currently responsible for starting all the defined caches in the {{preStartCaches()}} method. We might want to move this functionality to the generic server or to {{DefaultCacheManager}} itself. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues March 2020