You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Stephan Ewen (JIRA)" <ji...@apache.org> on 2018/08/06 10:23:00 UTC

[jira] [Commented] (FLINK-9973) Config property taskmanager.exit-on-fatal-akka-error is no longer used in Flip6

    [ https://issues.apache.org/jira/browse/FLINK-9973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16570008#comment-16570008 ] 

Stephan Ewen commented on FLINK-9973:
-------------------------------------

Is there ever a reason when we do not want to exit on a fatal akka error?
Should we just drop this option and always exit in a fatal error case?

> Config property taskmanager.exit-on-fatal-akka-error is no longer used in Flip6
> -------------------------------------------------------------------------------
>
>                 Key: FLINK-9973
>                 URL: https://issues.apache.org/jira/browse/FLINK-9973
>             Project: Flink
>          Issue Type: Bug
>          Components: TaskManager
>    Affects Versions: 1.5.0, 1.5.1, 1.5.2, 1.6.0
>            Reporter: Piotr Nowojski
>            Priority: Major
>
> TaskManagerOptions#EXIT_ON_FATAL_AKKA_ERROR is only referenced in legacy code. It should either be properly supported or documented/marked that's it's no longer supported in flip6. Ideally Flip6 should crash if user has specified it's value.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)