[
https://issues.apache.org/jira/browse/FLUME-1985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhouqingfa updated FLUME-1985:
------------------------------
Description:
why only can the files in the “spooling” directory transfer to sink one by
one? In case there files are very big and growthing real-time,then other files
can not transfer to sink.why thread pool only has one thread instead of
multiple?Could you consider "Executors.newScheduledThreadPool(n)" instead of
"Executors.newSingleThreadScheduledExecutor()"?
Look forward to your reply
was:
why only can the files in the “spooling” directory transfer to sink one by
one? In case there files are very big and growthing real-time,then other files
can not transfer to sink.why thread pool only has one thread instead of
multiple?Could you consider "Executors.newCachedThreadPool()" instead of
"Executors.newSingleThreadScheduledExecutor()"?
Look forward to your reply
> files in the “spooling” directory only can transfer to sink one by one.
> -----------------------------------------------------------------------
>
> Key: FLUME-1985
> URL: https://issues.apache.org/jira/browse/FLUME-1985
> Project: Flume
> Issue Type: Bug
> Components: Sinks+Sources
> Affects Versions: v1.4.0
> Reporter: zhouqingfa
> Fix For: v1.4.0
>
>
> why only can the files in the “spooling” directory transfer to sink one
> by one? In case there files are very big and growthing real-time,then other
> files can not transfer to sink.why thread pool only has one thread instead of
> multiple?Could you consider "Executors.newScheduledThreadPool(n)" instead of
> "Executors.newSingleThreadScheduledExecutor()"?
> Look forward to your reply
--
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
