[
https://issues.apache.org/jira/browse/FLUME-1511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13603250#comment-13603250
]
Hudson commented on FLUME-1511:
-------------------------------
Integrated in flume-trunk #377 (See
[https://builds.apache.org/job/flume-trunk/377/])
FLUME-1511. Scribe-source doesn't handle zero message request correctly.
(Revision 46dadc63e540bca52fe87557762506ed55cd5a3a)
Result = FAILURE
mpercy :
http://git-wip-us.apache.org/repos/asf/flume/repo?p=flume.git&a=commit&h=46dadc63e540bca52fe87557762506ed55cd5a3a
Files :
*
flume-ng-sources/flume-scribe-source/src/main/java/org/apache/flume/source/scribe/ScribeSource.java
> Scribe-source doesn't handle zero message request correctly.
> ------------------------------------------------------------
>
> Key: FLUME-1511
> URL: https://issues.apache.org/jira/browse/FLUME-1511
> Project: Flume
> Issue Type: Bug
> Components: Sinks+Sources
> Affects Versions: v1.2.0, v1.3.0
> Reporter: Xin Yu
> Assignee: Denny Ye
> Priority: Minor
> Labels: scribe, thrift
> Fix For: v1.4.0
>
> Attachments: FLUME-1511.patch
>
>
> ScribeSource deosn't handle the zero message request correctly.
> When scribed sends zero message request like this:
> sent <0> messages to remote scribe server <dwen:1564>
> The log receiver of scribe-source will return ResultCode.TRY_LATER.
> The return value reultes that scribed falls into infinite loop to
> retry to send the zero message request out, and the whole
> message channel is blocked.
> So I suggest that ResultCode.OK is returned when the size of
> LogEntry list is 0.
--
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
