[
https://issues.apache.org/jira/browse/FLUME-1382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13440195#comment-13440195
]
Xin Yu commented on FLUME-1382:
-------------------------------
ScribeSource didn't handle correctly for the zero message requests
from remote scribe server.
If scribed sends zero message request like:
sent <0> messages to remote scribe server <dwen:1564>
log receiver in ScribeSource will return ResultCode.TRY_LATER
and block whole transfer channel.
I seggest that return ResultCode.OK when the length of LogEntry's list.
> Flume adopt message from existing local Scribe
> ----------------------------------------------
>
> Key: FLUME-1382
> URL: https://issues.apache.org/jira/browse/FLUME-1382
> Project: Flume
> Issue Type: Improvement
> Components: Sinks+Sources
> Affects Versions: v1.2.0
> Reporter: Denny Ye
> Assignee: Denny Ye
> Priority: Minor
> Labels: scribe, thrift
> Fix For: v1.3.0
>
> Attachments: FLUME-1382-3.patch, FLUME-1382-doc-2.patch
>
>
> Currently, we are using Scribe in data ingest system. Central Scribe is hard
> to maintain and upgrade. Thus, we would like to replace central Scribe with
> Flume and adopt message from existing and amounts of local Scribe. This can
> be treated as legacy part.
> We have generated ScribeSource and used with more effective Thrift code
> without deserializing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
