[Red Hat JIRA] (ISPN-12607) Metrics degrade cluster performance
by Ryan Emerson (Jira)
[ https://issues.redhat.com/browse/ISPN-12607?page=com.atlassian.jira.plugi... ]
Ryan Emerson updated ISPN-12607:
--------------------------------
Security: (was: Red Hat Internal)
> Metrics degrade cluster performance
> -----------------------------------
>
> Key: ISPN-12607
> URL: https://issues.redhat.com/browse/ISPN-12607
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 12.0.0.CR1, 11.0.8.Final
> Reporter: Ryan Emerson
> Priority: Major
>
> The `/metrics` endpoint exposes Infinispan stats so that they can be periodically scraped by monitoring tools such as Prometheus. However, these stats include calls to `size` which does not perform well as the number of entries in a cache increase. Consequently, if deploying DG in a k8 environment with Prometheus monitoring the DG cluster performance rapidly declines as the number of entries in a cache increases due to time /resources spent iterating the cache container.
> This problem is only exasperated when muiltiple caches exist with many entries exist.
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 3 months
[Red Hat JIRA] (ISPN-12523) Obtaining internal caches from HotRod causes extra registration of SourceMigrators
by Gustavo Fernandes (Jira)
[ https://issues.redhat.com/browse/ISPN-12523?page=com.atlassian.jira.plugi... ]
Gustavo Fernandes updated ISPN-12523:
-------------------------------------
Affects Version/s: 11.0.8.Final
12.0.0.CR1
> Obtaining internal caches from HotRod causes extra registration of SourceMigrators
> ----------------------------------------------------------------------------------
>
> Key: ISPN-12523
> URL: https://issues.redhat.com/browse/ISPN-12523
> Project: Infinispan
> Issue Type: Bug
> Components: Hot Rod
> Affects Versions: 9.4.20.Final, 12.0.0.CR1, 11.0.8.Final
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
> Priority: Major
>
> Internal caches such as {{___protobuf_metadata}} always register a HotRodSourceMigrator when obtained via Hot Rod:
> {code:java}
> remotecacheManager.getCache(ProtobufMetadataManagerConstants.PROTOBUF_METADATA_CACHE_NAME)
> {code}
> This is because HotRod never adds internal caches to the knownCaches instance in order to check access to those caches. Regardless, it should not keep registering SourceMigrators everytime
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 3 months
[Red Hat JIRA] (ISPN-12523) Obtaining internal caches from HotRod causes extra registration of SourceMigrators
by Gustavo Fernandes (Jira)
[ https://issues.redhat.com/browse/ISPN-12523?page=com.atlassian.jira.plugi... ]
Work on ISPN-12523 started by Gustavo Fernandes.
------------------------------------------------
> Obtaining internal caches from HotRod causes extra registration of SourceMigrators
> ----------------------------------------------------------------------------------
>
> Key: ISPN-12523
> URL: https://issues.redhat.com/browse/ISPN-12523
> Project: Infinispan
> Issue Type: Bug
> Components: Hot Rod
> Affects Versions: 9.4.20.Final
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
> Priority: Major
>
> Internal caches such as {{___protobuf_metadata}} always register a HotRodSourceMigrator when obtained via Hot Rod:
> {code:java}
> remotecacheManager.getCache(ProtobufMetadataManagerConstants.PROTOBUF_METADATA_CACHE_NAME)
> {code}
> This is because HotRod never adds internal caches to the knownCaches instance in order to check access to those caches. Regardless, it should not keep registering SourceMigrators everytime
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 3 months
[Red Hat JIRA] (ISPN-12523) Obtaining internal caches from HotRod causes extra registration of SourceMigrators
by Gustavo Fernandes (Jira)
[ https://issues.redhat.com/browse/ISPN-12523?page=com.atlassian.jira.plugi... ]
Gustavo Fernandes updated ISPN-12523:
-------------------------------------
Status: Open (was: New)
> Obtaining internal caches from HotRod causes extra registration of SourceMigrators
> ----------------------------------------------------------------------------------
>
> Key: ISPN-12523
> URL: https://issues.redhat.com/browse/ISPN-12523
> Project: Infinispan
> Issue Type: Bug
> Components: Hot Rod
> Affects Versions: 9.4.20.Final
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
> Priority: Major
>
> Internal caches such as {{___protobuf_metadata}} always register a HotRodSourceMigrator when obtained via Hot Rod:
> {code:java}
> remotecacheManager.getCache(ProtobufMetadataManagerConstants.PROTOBUF_METADATA_CACHE_NAME)
> {code}
> This is because HotRod never adds internal caches to the knownCaches instance in order to check access to those caches. Regardless, it should not keep registering SourceMigrators everytime
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 3 months
[Red Hat JIRA] (ISPN-12606) REST configuration listeners
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-12606?page=com.atlassian.jira.plugi... ]
Tristan Tarrant updated ISPN-12606:
-----------------------------------
Description:
Add configuration event listeners to the REST endpoint.
These should use HTTP Server-Sent-Events
[https://html.spec.whatwg.org/multipage/server-sent-events.html|https://ht...]
h3. Configuration listeners:
{{GET /v2/server/config?action=listen[&includeCurrentState=true|false]}}
This will result in a response with content-type text/event-stream followed by a stream of configuration events.
Each event follows the following structure:
{noformat}
event: [cache|template|schema|task]
data: [json representantion of event]
{noformat}
the data field will contain a representation of the event:
* {{[cache|template|counter]-created}}: the full configuration of the entity
* {{[cache|template|counter]-removed}}: an empty string
* {{[schema]-created}}: the protobuf
* {{[schema]-removed}}: an empty string
This listener can be used by the operator to properly implement reconciliation of CRs when the entities they refer to are created/modified via other means (API, CLI, Console).
was:
Add configuration event listeners to the REST endpoint.
These should use HTTP Server-Sent-Events
[https://html.spec.whatwg.org/multipage/server-sent-events.html|https://ht...]
h3. Configuration listeners:
{{GET /v2/server/config?action=listen[&includeCurrentState=true|false]}}
This will result in a response with content-type text/event-stream followed by a stream of configuration events.
Each event follows the following structure:
{noformat}
event: [cache|template|schema|task]
data: [json representantion of event]
{noformat}
the data field will contain a representation of the event:
* {{[cache|template|counter]-created}}: the full configuration of the entity
* {{[cache|template|counter]-removed}}: an empty string
* {{[schema]-created}}: the protobuf
* {{[schema]-removed}}: an empty string
> REST configuration listeners
> ----------------------------
>
> Key: ISPN-12606
> URL: https://issues.redhat.com/browse/ISPN-12606
> Project: Infinispan
> Issue Type: Feature Request
> Components: Listeners, REST, Server
> Reporter: Tristan Tarrant
> Priority: Major
>
> Add configuration event listeners to the REST endpoint.
> These should use HTTP Server-Sent-Events
> [https://html.spec.whatwg.org/multipage/server-sent-events.html|https://ht...]
> h3. Configuration listeners:
> {{GET /v2/server/config?action=listen[&includeCurrentState=true|false]}}
> This will result in a response with content-type text/event-stream followed by a stream of configuration events.
> Each event follows the following structure:
> {noformat}
> event: [cache|template|schema|task]
> data: [json representantion of event]
> {noformat}
> the data field will contain a representation of the event:
> * {{[cache|template|counter]-created}}: the full configuration of the entity
> * {{[cache|template|counter]-removed}}: an empty string
> * {{[schema]-created}}: the protobuf
> * {{[schema]-removed}}: an empty string
> This listener can be used by the operator to properly implement reconciliation of CRs when the entities they refer to are created/modified via other means (API, CLI, Console).
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 3 months
[Red Hat JIRA] (ISPN-12606) REST configuration listeners
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-12606?page=com.atlassian.jira.plugi... ]
Tristan Tarrant updated ISPN-12606:
-----------------------------------
Description:
Add configuration event listeners to the REST endpoint.
These should use HTTP Server-Sent-Events
[https://html.spec.whatwg.org/multipage/server-sent-events.html|https://ht...]
h3. Configuration listeners:
{{GET /v2/server/config?action=listen[&includeCurrentState=true|false]}}
This will result in a response with content-type text/event-stream followed by a stream of configuration events.
Each event follows the following structure:
{noformat}
event: [cache|template|schema|task]
data: [json representantion of event]
{noformat}
the data field will contain a representation of the event:
* {{[cache|template|counter]-created}}: the full configuration of the entity
* {{[cache|template|counter]-removed}}: an empty string
* {{[schema]-created}}: the protobuf
* {{[schema]-removed}}: an empty string
was:
Add configuration event listeners to the REST endpoint.
These should use HTTP Server-Sent-Events
[https://html.spec.whatwg.org/multipage/server-sent-events.html|https://ht...]
h3. Configuration listeners:
{{GET /v2/server/config?action=listen[&includeCurrentState=true|false]}}
This will result in a response with content-type text/event-stream followed by a stream of configuration events.
Each event follows the following structure:
{noformat}
event: [cache|template|schema|task]
data: [json representantion of event]
{noformat}
the data field will contain a representation of the event:
* [cache|template|counter]-created: the full configuration of the entity
* [cache|template|counter]-removed: an empty string
* [schema]-created: the protobuf
* [schema]-removed: an empty string
> REST configuration listeners
> ----------------------------
>
> Key: ISPN-12606
> URL: https://issues.redhat.com/browse/ISPN-12606
> Project: Infinispan
> Issue Type: Feature Request
> Components: Listeners, REST, Server
> Reporter: Tristan Tarrant
> Priority: Major
>
> Add configuration event listeners to the REST endpoint.
> These should use HTTP Server-Sent-Events
> [https://html.spec.whatwg.org/multipage/server-sent-events.html|https://ht...]
> h3. Configuration listeners:
> {{GET /v2/server/config?action=listen[&includeCurrentState=true|false]}}
> This will result in a response with content-type text/event-stream followed by a stream of configuration events.
> Each event follows the following structure:
> {noformat}
> event: [cache|template|schema|task]
> data: [json representantion of event]
> {noformat}
> the data field will contain a representation of the event:
> * {{[cache|template|counter]-created}}: the full configuration of the entity
> * {{[cache|template|counter]-removed}}: an empty string
> * {{[schema]-created}}: the protobuf
> * {{[schema]-removed}}: an empty string
--
This message was sent by Atlassian Jira
(v8.13.1#813001)
5 years, 3 months