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/AMRunner.java:110

  public void startAM() throws YarnException, IOException {
    switch (inputType) {
      case SLS:
        for (String inputTrace : inputTraces) {
          startAMFromSLSTrace(inputTrace);
        }
        break;
      case RUMEN:
        long baselineTimeMS = 0;
        for (String inputTrace : inputTraces) {
          startAMFromRumenTrace(inputTrace, baselineTimeMS);
        }
        break;
      case SYNTH:
        startAMFromSynthGenerator();
        break;
      default:
        throw new YarnException("Input configuration not recognized, "
            + "trace type should be SLS, RUMEN, or SYNTH");
    }

    numAMs = amMap.size();
    remainingApps = numAMs;
  }

  /**
   * Parse workload from a SLS trace file.
   */
  private void startAMFromSLSTrace(String inputTrace) throws IOException {
    JsonFactory jsonF = new JsonFactory();
    ObjectMapper mapper = new ObjectMapper();

    try (Reader input = new InputStreamReader(
        new FileInputStream(inputTrace), StandardCharsets.UTF_8)) {
      JavaType type = mapper.getTypeFactory().
          constructMapType(Map.class, String.class, String.class);

View on GitHub (pinned to 2add963021)

Solutions

1. Set sls.trace.type (input 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 AM 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/414604ceaab0ba3a. Report an issue: GitHub.