[
https://issues.apache.org/jira/browse/FLUME-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13590196#comment-13590196
]
Hudson commented on FLUME-1925:
-------------------------------
Integrated in flume-trunk #365 (See
[https://builds.apache.org/job/flume-trunk/365/])
FLUME-1925. HDFS timeouts should not starve other threads. (Revision
ed4cae79f8ab66a71960dfa2bdb848f8141ca6bd)
Result = SUCCESS
mpercy :
http://git-wip-us.apache.org/repos/asf/flume/repo?p=flume.git&a=commit&h=ed4cae79f8ab66a71960dfa2bdb848f8141ca6bd
Files :
*
flume-ng-sinks/flume-hdfs-sink/src/test/java/org/apache/flume/sink/hdfs/TestBucketWriter.java
*
flume-ng-sinks/flume-hdfs-sink/src/main/java/org/apache/flume/sink/hdfs/BucketWriter.java
*
flume-ng-sinks/flume-hdfs-sink/src/main/java/org/apache/flume/sink/hdfs/HDFSEventSink.java
> HDFS timeouts should not starve other threads
> ---------------------------------------------
>
> Key: FLUME-1925
> URL: https://issues.apache.org/jira/browse/FLUME-1925
> Project: Flume
> Issue Type: Bug
> Reporter: Hari Shreedharan
> Assignee: Hari Shreedharan
> Fix For: v1.4.0
>
> Attachments: FLUME-1925-1.patch, FLUME-1925.patch
>
>
> Currently it is possible to have one HDFS call cause another one from timing
> out because of the synchronized blocks inside the HDFS sink code. So when we
> calculate timeout, we end up calculating the time to enter the monitor + hdfs
> calls. We must change it to make sure only the HDFS calls count towards the
> timeout.
--
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
