You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bookkeeper.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2014/02/22 18:53:19 UTC
[jira] [Commented] (BOOKKEEPER-735) Merge PerChannelBookieClient
goodness from trunk to 4.2 branch
[ https://issues.apache.org/jira/browse/BOOKKEEPER-735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13909453#comment-13909453 ]
Hadoop QA commented on BOOKKEEPER-735:
--------------------------------------
Testing JIRA BOOKKEEPER-735
Patch [0001-BOOKKEEPER-735_br_4_2.patch|https://issues.apache.org/jira/secure/attachment/12630486/0001-BOOKKEEPER-735_br_4_2.patch] downloaded at Sat Feb 22 17:51:28 UTC 2014
----------------------------
{color:red}-1{color} Patch failed to apply to head of branch
----------------------------
> Merge PerChannelBookieClient goodness from trunk to 4.2 branch
> --------------------------------------------------------------
>
> Key: BOOKKEEPER-735
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-735
> Project: Bookkeeper
> Issue Type: Bug
> Components: bookkeeper-client
> Affects Versions: 4.2.2
> Reporter: Rakesh R
> Assignee: Rakesh R
> Fix For: 4.2.3
>
> Attachments: 0001-BOOKKEEPER-735_br_4_2.patch
>
>
> In trunk we have done good imprv/bug fixes to perChannelBookieClient, I feel its worth to merge the necessary changes into 4.2 branch too.
> Included the following jira issues:
> # BOOKKEEPER-688
> # BOOKKEEPER-714
> # BOOKKEEPER-726
> # BOOKKEEPER-602 (from this, merge the logging of timed out entries).
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)