[JBoss JIRA] (ISPN-10018) Observability: clean up logging categories
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-10018?page=com.atlassian.jira.plugin... ]
Tristan Tarrant updated ISPN-10018:
-----------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/infinispan/infinispan/pull/7383
> Observability: clean up logging categories
> ------------------------------------------
>
> Key: ISPN-10018
> URL: https://issues.jboss.org/browse/ISPN-10018
> Project: Infinispan
> Issue Type: Sub-task
> Components: JMX, reporting and management
> Affects Versions: 10.0.0.Beta2
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Major
> Fix For: 10.0.0.Final
>
>
> For logs with level INFO, WARN, ERROR, FATAL we want to use specific categories instead of the fully-qualified class name.
> The following is a list of categories:
> * org.infinispan.CLUSTER: messages related to clustering (state transfer, rebalancing, partitioning, etc)
> * org.infinispan.CONFIG: messages related to configuration
> * org.infinispan.PERSISTENCE: messages related to loaders/stores
> * org.infinispan.SECURITY: messages related to security
> * org.infinispan.CONTAINER: messages related to the data container (e.g. expiration, eviction, listeners, transactions, etc)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 2 months
[JBoss JIRA] (ISPN-10018) Observability: clean up logging categories
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-10018?page=com.atlassian.jira.plugin... ]
Tristan Tarrant updated ISPN-10018:
-----------------------------------
Status: Open (was: New)
> Observability: clean up logging categories
> ------------------------------------------
>
> Key: ISPN-10018
> URL: https://issues.jboss.org/browse/ISPN-10018
> Project: Infinispan
> Issue Type: Sub-task
> Components: JMX, reporting and management
> Affects Versions: 10.0.0.Beta2
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Major
> Fix For: 10.0.0.Final
>
>
> For logs with level INFO, WARN, ERROR, FATAL we want to use specific categories instead of the fully-qualified class name.
> The following is a list of categories:
> * org.infinispan.CLUSTER: messages related to clustering (state transfer, rebalancing, partitioning, etc)
> * org.infinispan.CONFIG: messages related to configuration
> * org.infinispan.PERSISTENCE: messages related to loaders/stores
> * org.infinispan.SECURITY: messages related to security
> * org.infinispan.CONTAINER: messages related to the data container (e.g. expiration, eviction, listeners, transactions, etc)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 2 months
[JBoss JIRA] (ISPN-10018) Observability: clean up logging categories
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-10018?page=com.atlassian.jira.plugin... ]
Tristan Tarrant reassigned ISPN-10018:
--------------------------------------
Assignee: Tristan Tarrant (was: Nistor Adrian)
> Observability: clean up logging categories
> ------------------------------------------
>
> Key: ISPN-10018
> URL: https://issues.jboss.org/browse/ISPN-10018
> Project: Infinispan
> Issue Type: Sub-task
> Components: JMX, reporting and management
> Affects Versions: 10.0.0.Beta2
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Major
> Fix For: 10.0.0.Final
>
>
> For logs with level INFO, WARN, ERROR, FATAL we want to use specific categories instead of the fully-qualified class name.
> The following is a list of categories:
> * org.infinispan.CLUSTER: messages related to clustering (state transfer, rebalancing, partitioning, etc)
> * org.infinispan.CONFIG: messages related to configuration
> * org.infinispan.PERSISTENCE: messages related to loaders/stores
> * org.infinispan.SECURITY: messages related to security
> * org.infinispan.CONTAINER: messages related to the data container (e.g. expiration, eviction, listeners, transactions, etc)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 2 months
[JBoss JIRA] (ISPN-10706) StateTransfer should complete segments as they are transferred.
by Will Burns (Jira)
[ https://issues.jboss.org/browse/ISPN-10706?page=com.atlassian.jira.plugin... ]
Will Burns updated ISPN-10706:
------------------------------
Description:
State Transfer today sends entries by a given set of segments it owns. This means it will not complete the transfer until all entries for all the given segments are complete. Instead we should be a bit smarter and complete segments as they are sent, since we can efficiently iterate over a given set of segments.
The main problematic part is if we don't have a segmented store and `fetchPersistentState` is enabled. In this case we would need to do the current behavior.
We also can then remove references in the CommitManager by segment, instead of retaining all keys for the given set of segments.
> StateTransfer should complete segments as they are transferred.
> ---------------------------------------------------------------
>
> Key: ISPN-10706
> URL: https://issues.jboss.org/browse/ISPN-10706
> Project: Infinispan
> Issue Type: Enhancement
> Reporter: Will Burns
> Priority: Major
>
> State Transfer today sends entries by a given set of segments it owns. This means it will not complete the transfer until all entries for all the given segments are complete. Instead we should be a bit smarter and complete segments as they are sent, since we can efficiently iterate over a given set of segments.
> The main problematic part is if we don't have a segmented store and `fetchPersistentState` is enabled. In this case we would need to do the current behavior.
> We also can then remove references in the CommitManager by segment, instead of retaining all keys for the given set of segments.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 2 months