[JBoss JIRA] (ISPN-5285) Logging for Partition Handling and Key availablility too verbose
by Wolf-Dieter Fink (JIRA)
[ https://issues.jboss.org/browse/ISPN-5285?page=com.atlassian.jira.plugin.... ]
Wolf-Dieter Fink commented on ISPN-5285:
----------------------------------------
BTW as this messages are related to the cluster or cache, what about to move to the org.infinispan.CLUSTER || CACHE?
> Logging for Partition Handling and Key availablility too verbose
> ----------------------------------------------------------------
>
> Key: ISPN-5285
> URL: https://issues.jboss.org/browse/ISPN-5285
> Project: Infinispan
> Issue Type: Enhancement
> Reporter: Wolf-Dieter Fink
>
> If, during a cluster spit, the partitions are in DEGRADED mode, access to a key is logged in TRACE and ERROR, but the ERROR seems too verbose.
> TRACE Checking availablility for key=...., status DEGRADED_MODE
> TRACE Part. in DEGRADED_MODE, access is not allowed for key ....
> ERROR ISPN0000306, Key '...' not available. Not all owners .....
> and a full stacktrace
> Logging the information twice in DEBUG and ERROR seems useless.
> But having the full stacktrace might blow up the log file during DEGRADED_MODE. The error should only one line, no stacktrace as this information is not very useful at this point.
> Maybe a TRACE message or lower should include the stacktrace if there is a need for this information.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (ISPN-5273) Add more test scenarios for HR event listeners
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/ISPN-5273?page=com.atlassian.jira.plugin.... ]
Galder Zamarreño updated ISPN-5273:
-----------------------------------
Status: Resolved (was: Pull Request Sent)
Fix Version/s: 7.2.0.Beta1
Resolution: Done
> Add more test scenarios for HR event listeners
> ----------------------------------------------
>
> Key: ISPN-5273
> URL: https://issues.jboss.org/browse/ISPN-5273
> Project: Infinispan
> Issue Type: Task
> Components: Test Suite - Core
> Reporter: Vojtech Juranek
> Assignee: Vojtech Juranek
> Fix For: 7.2.0.Beta1
>
>
> Add following test scenarios:
> * custom events can contain more information than key, value and metadata
> * client can recognize the order of changes on given key
> * client receive failover event upon failover (already covered in tests) and then starts receiving evens from another server
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (ISPN-5244) Verify container and cluster-wide cache stats
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/ISPN-5244?page=com.atlassian.jira.plugin.... ]
Galder Zamarreño updated ISPN-5244:
-----------------------------------
Affects Version/s: 7.1.1.Final
> Verify container and cluster-wide cache stats
> ---------------------------------------------
>
> Key: ISPN-5244
> URL: https://issues.jboss.org/browse/ISPN-5244
> Project: Infinispan
> Issue Type: Bug
> Components: JMX, reporting and management
> Affects Versions: 7.1.1.Final
> Reporter: Vladimir Blagojevic
> Assignee: Vladimir Blagojevic
> Priority: Minor
> Fix For: 7.2.0.Beta1, 7.2.0.Final
>
>
> In container cache stats we sometimes blindly aggregate cache stats which can lead to unusual results in some specific situations. For example, we add numberOfEntries across all caches but numberOfEntries stat for caches is initialized with value of -1. Therefore adding such values results in negative total numberOfEntries for container stats which users will confuse users.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (ISPN-5244) Verify container and cluster-wide cache stats
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/ISPN-5244?page=com.atlassian.jira.plugin.... ]
Galder Zamarreño updated ISPN-5244:
-----------------------------------
Status: Open (was: New)
> Verify container and cluster-wide cache stats
> ---------------------------------------------
>
> Key: ISPN-5244
> URL: https://issues.jboss.org/browse/ISPN-5244
> Project: Infinispan
> Issue Type: Bug
> Components: JMX, reporting and management
> Affects Versions: 7.1.1.Final
> Reporter: Vladimir Blagojevic
> Assignee: Vladimir Blagojevic
> Priority: Minor
> Fix For: 7.2.0.Beta1, 7.2.0.Final
>
>
> In container cache stats we sometimes blindly aggregate cache stats which can lead to unusual results in some specific situations. For example, we add numberOfEntries across all caches but numberOfEntries stat for caches is initialized with value of -1. Therefore adding such values results in negative total numberOfEntries for container stats which users will confuse users.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (ISPN-5244) Verify container and cluster-wide cache stats
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/ISPN-5244?page=com.atlassian.jira.plugin.... ]
Galder Zamarreño updated ISPN-5244:
-----------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/infinispan/infinispan/pull/3267
> Verify container and cluster-wide cache stats
> ---------------------------------------------
>
> Key: ISPN-5244
> URL: https://issues.jboss.org/browse/ISPN-5244
> Project: Infinispan
> Issue Type: Bug
> Components: JMX, reporting and management
> Affects Versions: 7.1.1.Final
> Reporter: Vladimir Blagojevic
> Assignee: Vladimir Blagojevic
> Priority: Minor
> Fix For: 7.2.0.Beta1, 7.2.0.Final
>
>
> In container cache stats we sometimes blindly aggregate cache stats which can lead to unusual results in some specific situations. For example, we add numberOfEntries across all caches but numberOfEntries stat for caches is initialized with value of -1. Therefore adding such values results in negative total numberOfEntries for container stats which users will confuse users.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (ISPN-5244) Verify container and cluster-wide cache stats
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/ISPN-5244?page=com.atlassian.jira.plugin.... ]
Galder Zamarreño updated ISPN-5244:
-----------------------------------
Status: Resolved (was: Pull Request Sent)
Fix Version/s: 7.2.0.Final
Resolution: Done
> Verify container and cluster-wide cache stats
> ---------------------------------------------
>
> Key: ISPN-5244
> URL: https://issues.jboss.org/browse/ISPN-5244
> Project: Infinispan
> Issue Type: Bug
> Components: JMX, reporting and management
> Affects Versions: 7.1.1.Final
> Reporter: Vladimir Blagojevic
> Assignee: Vladimir Blagojevic
> Priority: Minor
> Fix For: 7.2.0.Beta1, 7.2.0.Final
>
>
> In container cache stats we sometimes blindly aggregate cache stats which can lead to unusual results in some specific situations. For example, we add numberOfEntries across all caches but numberOfEntries stat for caches is initialized with value of -1. Therefore adding such values results in negative total numberOfEntries for container stats which users will confuse users.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years