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

Hadoop QA commented on BOOKKEEPER-602:
--------------------------------------

Testing JIRA BOOKKEEPER-602


Patch 
[BOOKKEEPER-602.diff|https://issues.apache.org/jira/secure/attachment/12591098/BOOKKEEPER-602.diff]
 downloaded at Sun Jul  7 02:37:36 UTC 2013

----------------------------

{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+1 RAW_PATCH_ANALYSIS{color}
.    {color:green}+1{color} the patch does not introduce any @author tags
.    {color:green}+1{color} the patch does not introduce any tabs
.    {color:green}+1{color} the patch does not introduce any trailing spaces
.    {color:green}+1{color} the patch does not introduce any line longer than 
120
.    {color:green}+1{color} the patch does adds/modifies 3 testcase(s)
{color:green}+1 RAT{color}
.    {color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.    {color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:green}+1 COMPILE{color}
.    {color:green}+1{color} HEAD compiles
.    {color:green}+1{color} patch compiles
.    {color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1 FINDBUGS{color}
.    {color:green}+1{color} the patch does not seem to introduce new Findbugs 
warnings
{color:red}-1 TESTS{color}
.    Tests run: 853
.    Tests failed: 1
.    Tests errors: 0

.    The patch failed the following testcases:

.      testDeadlock(org.apache.hedwig.server.persistence.TestDeadlock)

{color:green}+1 DISTRO{color}
.    {color:green}+1{color} distro tarball builds with the patch 

----------------------------
{color:red}*-1 Overall result, please check the reported -1(s)*{color}


The full output of the test-patch run is available at

.   https://builds.apache.org/job/bookkeeper-trunk-precommit-build/416/
                
> we should have request timeouts rather than channel timeout in 
> PerChannelBookieClient
> -------------------------------------------------------------------------------------
>
>                 Key: BOOKKEEPER-602
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-602
>             Project: Bookkeeper
>          Issue Type: Bug
>    Affects Versions: 4.2.0, 4.2.1
>            Reporter: Sijie Guo
>             Fix For: 4.3.0
>
>         Attachments: BOOKKEEPER-602.diff
>
>
> currently we only have readTimeout in netty channel, it timeouts only when 
> there is no activities in that channel, but it can't track timeouts of 
> individual requests. if a channel continues having read entry activities, it 
> might shadow a slow add entry response, which is bad impacting add latency.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to