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

Posted to dev@apex.apache.org by "Sandesh (JIRA)" <ji...@apache.org> on 2016/10/04 21:07:20 UTC

[jira] [Created] (APEXCORE-547) Strict & lenient Physical Plan checking

Sandesh created APEXCORE-547:
--------------------------------

             Summary: Strict & lenient Physical Plan checking
                 Key: APEXCORE-547
                 URL: https://issues.apache.org/jira/browse/APEXCORE-547
             Project: Apache Apex Core
          Issue Type: Improvement
            Reporter: Sandesh


This will need a bigger discussion, filing here so that it can be tracked.

Example:

Container max memory is set by yarn settings. So multiple operators in a container with the high memory requirement may not get the sufficient memory, as Apex just allocates the yarn allowed max memory and launches the application. 

Users should have a control saying don't launch the app if memory requirements are not set.







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