apache/hadoop · error · YarnException

Input configuration not recognized, trace type should be SLS

Error message

Input configuration not recognized, trace type should be SLS, RUMEN, or SYNTH

What it means

Error "Input configuration not recognized, trace type should be SLS, RUMEN, or SYNTH" thrown in apache/hadoop.

Source

Thrown at hadoop-tools/hadoop-sls/src/main/java/org/apache/hadoop/yarn/sls/NMRunner.java:104

        SLSConfiguration.NM_RESOURCE_UTILIZATION_RATIO_DEFAULT);
    // nm information (fetch from topology file, or from sls/rumen json file)
    Set<SLSRunner.NodeDetails> nodeSet = null;
    if (nodeFile.isEmpty()) {
      for (String inputTrace : inputTraces) {
        switch (inputType) {
          case SLS:
            nodeSet = SLSUtils.parseNodesFromSLSTrace(inputTrace);
            break;
          case RUMEN:
            nodeSet = SLSUtils.parseNodesFromRumenTrace(inputTrace);
            break;
          case SYNTH:
            stjp = new SynthTraceJobProducer(conf, new Path(inputTraces[0]));
            nodeSet = SLSUtils.generateNodes(stjp.getNumNodes(),
                stjp.getNumNodes()/stjp.getNodesPerRack());
            break;
          default:
            throw new YarnException("Input configuration not recognized, "
                + "trace type should be SLS, RUMEN, or SYNTH");
        }
      }
    } else {
      nodeSet = SLSUtils.parseNodesFromNodeFile(nodeFile,
          nodeManagerResource);
    }

    if (nodeSet == null || nodeSet.isEmpty()) {
      throw new YarnException("No node! Please configure nodes.");
    }

    SLSUtils.generateNodeTableMapping(nodeSet, tableMapping);

    // create NM simulators
    Random random = new Random();
    Set<String> rackSet = ConcurrentHashMap.newKeySet();
    int threadPoolSize = Math.max(this.threadPoolSize,

View on GitHub (pinned to 2add963021)

Solutions

1. Set the NM input trace type to one of SLS, RUMEN, or SYNTH.

When it happens

Trigger: The SLS input configuration specifies a trace type other than SLS, RUMEN, or SYNTH, so the NM runner cannot interpret the input.

Common situations: See trigger scenarios.

AI-assisted analysis of apache/hadoop@2add963021 (2026-08-22). Data as JSON: /api/errors/9889dde8a5b85cda. Report an issue: GitHub.