[
https://issues.apache.org/jira/browse/FLINK-930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14033588#comment-14033588
]
ASF GitHub Bot commented on FLINK-930:
--------------------------------------
Github user uce commented on the pull request:
https://github.com/apache/incubator-flink/pull/19#issuecomment-46284531
I agree with both your points and have addressed them. The thrown
exceptions are rethrown as IOExceptions up to the TaskManager's shutdown
method, where it is logged. I decided against changing the signature of the
TaskManager's shutdown method to rethrow the Exception as I think this should
go hand in hand with changes to the other component shutdowns as well.
> Netty Initialization is sometimes very slow
> -------------------------------------------
>
> Key: FLINK-930
> URL: https://issues.apache.org/jira/browse/FLINK-930
> Project: Flink
> Issue Type: Bug
> Reporter: Stephan Ewen
> Assignee: Ufuk Celebi
> Labels: performance
>
> I often see the initialization of Netty taking 3 seconds and then failing
> with the message
> "WARN io.netty.util.internal.ThreadLocalRandom - Failed
> to generate a seed from SecureRandom within 3 seconds. Not enough entrophy?"
> This adds to every single run a 3 seconds delay, which is often more than the
> test time and causes our builds to run out of time.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
