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 "Alex Parvulescu (JIRA)" <ji...@apache.org> on 2014/12/15 14:04:14 UTC

[jira] [Created] (OAK-2355) TarMK Cold Standby expose standby read timeout value

Alex Parvulescu created OAK-2355:
------------------------------------

             Summary: TarMK Cold Standby expose standby read timeout value
                 Key: OAK-2355
                 URL: https://issues.apache.org/jira/browse/OAK-2355
             Project: Jackrabbit Oak
          Issue Type: Bug
          Components: segmentmk
            Reporter: Alex Parvulescu
            Assignee: Alex Parvulescu
             Fix For: 1.0.9, 1.1.4


Running into a read timeout on the standby instance logs some uncaught error:
{code}
org.apache.jackrabbit.oak.plugins.segment.standby.client.SegmentLoaderHandler Exception caught, closing channel.
io.netty.handler.timeout.ReadTimeoutException: null
{code}

I'm not sure how/if I need to fix this, the sync process will pickup again, but we can expose the timeout value, so if the network connection is known to be poor, a client can increase the timeout to work around this issue.





--
This message was sent by Atlassian JIRA
(v6.3.4#6332)