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 "Marcel Reutegger (JIRA)" <ji...@apache.org> on 2019/04/10 07:55:00 UTC

[jira] [Updated] (OAK-8202) RemoteBlobProcessor should print a stack trace of the exceptions it swallows

     [ https://issues.apache.org/jira/browse/OAK-8202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marcel Reutegger updated OAK-8202:
----------------------------------
    Fix Version/s:     (was: 1.10.3)
                   1.12.0

Adjusted the fix version to 1.12.0. The change went into trunk before 1.12.0 was released.

> RemoteBlobProcessor should print a stack trace of the exceptions it swallows
> ----------------------------------------------------------------------------
>
>                 Key: OAK-8202
>                 URL: https://issues.apache.org/jira/browse/OAK-8202
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: segment-tar
>            Reporter: Francesco Mari
>            Assignee: Francesco Mari
>            Priority: Major
>             Fix For: 1.12.0
>
>
> In order to cope with the dryness of the {{BlobStore}} and {{DataStore}} API, {{RemoteBlobProcessor#shouldFetchBinary}} relies on exceptions to implement part of its logic. While this is a bad development practice, it was the only way to cope with in-memory binary IDs without spending excessive amounts of network and CPU. To Improve the transparency of the system, {{RemoteBlobProcessor}} should print a message at WARN level every time it swallows an exception.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)