[
https://issues.apache.org/jira/browse/BOOKKEEPER-735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13918378#comment-13918378
]
Rakesh R commented on BOOKKEEPER-735:
-------------------------------------
Yeah fine Sijie, no issues for me. I'd like to see these fixes in branch 4.2 as
well. I'll reopen it and will add my comments.
Actually last week I hit BOOKKEEPER-734 issue in my cluster. When analyzing the
same I have noticed some of these useful changes which is committed only in the
trunk version and is not present in branch 4.2. In some other project, I've
seen similar patterns of backporting fixes from trunk to other branches. So I
thought it would be helpful for the committers to commit the changes using a
single patch.
Also, appreciate the contributors those who spends their time and done good
contributions by raise/fix/reviewing of these issues.
> 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.2#6252)
