You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@apex.apache.org by "Sanjay M Pujare (JIRA)" <ji...@apache.org> on 2016/10/26 23:52:58 UTC

[jira] [Commented] (APEXCORE-565) Ability to activate and de-activate operators in the DAG

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

Sanjay M Pujare commented on APEXCORE-565:
------------------------------------------

When will inactive operators be activated? Are there automation use cases where operators (and streams) will be activated based on a condition/event that happens in the application itself?

> Ability to activate and de-activate operators in the DAG
> --------------------------------------------------------
>
>                 Key: APEXCORE-565
>                 URL: https://issues.apache.org/jira/browse/APEXCORE-565
>             Project: Apache Apex Core
>          Issue Type: New Feature
>            Reporter: Vlad Rozov
>
> Currently, there is no ability to mark operators/streams as inactive and activate or de-activate them at run-time based on a condition or event. It should be possible to statically populate DAG, but mark some operators as inactive, so stram app master will not allocate physical nodes for inactive operators and will not request containers from Yarn or any other resource manager. This will allow to save resources and better support batch operations in Apex.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)