[infinispan-issues] [JBoss JIRA] (ISPN-5285) Logging for Partition Handling and Key availablility too verbose

[Wolf-Dieter Fink (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-5285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13049554#comment-13049554 ] 

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)