You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@distributedlog.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/07/27 00:22:20 UTC

[jira] [Commented] (DL-20) Validate bk read timeout in distributedlog configuration

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

ASF GitHub Bot commented on DL-20:
----------------------------------

GitHub user yzang opened a pull request:

    https://github.com/apache/incubator-distributedlog/pull/4

    DL-20: Validate bk read timeout in configuration

    DL-20: Ensure bkcReadTimeoutSeconds is larger than readLACLongPollTimeout

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/yzang/incubator-distributedlog yzang/validate_configuration

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-distributedlog/pull/4.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #4
    
----
commit 8daa541891da320910f195efc9d6ba7207ab88af
Author: Yiming Zang <yz...@twitter.com>
Date:   2016-07-18T21:49:59Z

    Validate bk read timeout in configuration
    
    RB_ID=852868

----


> Validate bk read timeout in distributedlog configuration
> --------------------------------------------------------
>
>                 Key: DL-20
>                 URL: https://issues.apache.org/jira/browse/DL-20
>             Project: DistributedLog
>          Issue Type: Bug
>          Components: distributedlog-core
>            Reporter: Yiming Zang
>            Assignee: Yiming Zang
>            Priority: Minor
>             Fix For: 0.4.0
>
>
> we need to ensure bkcReadTimeoutSeconds is larger than readLACLongPollTimeout, otherwise the long poll read requests will just keep timeout when there is not traffic.



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