You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Axel Hanikel (Jira)" <ji...@apache.org> on 2020/09/08 09:34:00 UTC

[jira] [Commented] (OAK-9201) PersistentRedisCache: failure to write segment is not an error

    [ https://issues.apache.org/jira/browse/OAK-9201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17192075#comment-17192075 ] 

Axel Hanikel commented on OAK-9201:
-----------------------------------

[~adulceanu] WDYT?

> PersistentRedisCache: failure to write segment is not an error
> --------------------------------------------------------------
>
>                 Key: OAK-9201
>                 URL: https://issues.apache.org/jira/browse/OAK-9201
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: segment-azure
>    Affects Versions: 1.34.0
>            Reporter: Axel Hanikel
>            Priority: Minor
>              Labels: patch
>             Fix For: 1.36.0
>
>         Attachments: 0001-OAK-9201-PersistentRedisCache-failure-to-write-segme.patch
>
>
> Failure to write a segment to the redis cache results in an error level log message with a stack trace. However, this is expected behaviour: socket timeouts prevent the cache from effectively slowing down a request. OTOH too many socket timeouts make the cache ineffective, so it's good to have a way to log such errors when debugging. My suggestion is therefore to change the log level to "debug" and avoid the stack trace.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)