apex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ishark <...@git.apache.org>
Subject [GitHub] incubator-apex-core pull request: APEX-92 Fixing Configuration of ...
Date Wed, 07 Oct 2015 23:19:59 GMT
Github user ishark commented on a diff in the pull request:

    --- Diff: engine/src/main/java/com/datatorrent/stram/StreamingAppMasterService.java ---
    @@ -647,8 +645,8 @@ private void execute() throws YarnException, IOException
         int minVcores = conf.getInt("yarn.scheduler.minimum-allocation-vcores", 0);
         LOG.info("Max mem {}m, Min mem {}m, Max vcores {} and Min vcores {} capabililty of
resources in this cluster ", maxMem, minMem, maxVcores, minVcores);
    -    int maxConsecutiveContainerFailures = conf.getInt("MAX_CONSECUTIVE_CONTAINER_FAILURES",
    -    long blacklistRemovalTime = conf.getLong("BLACKLIST_REMOVAL_TIME", BLACKLIST_REMOVAL_TIME);
    +    int maxConsecutiveContainerFailures = dag.getValue(LogicalPlan.MAX_CONSECUTIVE_CONTAINER_FAILURES);
    --- End diff --
    Yes, have tested this in cluster. It can be set through conf with this: 
    Or by directly setting inside populateDag: conf.setInt("dt.max-consecutive-node-failures",

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.

View raw message