apache/hadoop · error · InvalidInputException

Solver timeInterval is non-positive, please try again with v

Error message

Solver timeInterval is non-positive, please try again with valid Solver timeInterval

What it means

Error "Solver timeInterval is non-positive, please try again with valid Solver timeInterval" thrown in apache/hadoop.

Source

Thrown at hadoop-tools/hadoop-resourceestimator/src/main/java/org/apache/hadoop/resourceestimator/solver/preprocess/SolverPreprocessor.java:74

   * @throws InvalidInputException if: (1) jobHistory is <em>null</em>;
   *     (2) jobHistory is empty; (3) timeout is non-positive;
   *     (4) timeInterval is non-positive;
   */
  public final void validate(
      final Map<RecurrenceId, List<ResourceSkyline>> jobHistory,
      final int timeInterval) throws InvalidInputException {
    if ((jobHistory == null) || (jobHistory.size() == 0)) {
      LOGGER.error(
          "Job resource skyline history is invalid, please try again with"
              + " valid resource skyline history.");
      throw new InvalidInputException("Job ResourceSkyline history", "invalid");
    }

    if (timeInterval <= 0) {
      LOGGER.error(
          "Solver timeInterval {} is invalid, please specify a positive value.",
          timeInterval);
      throw new InvalidInputException("Solver timeInterval", "non-positive");
    }
  }

  /**
   * Return the multi-dimension resource vector consumed by the job at specified
   * time.
   *
   * @param skyList           the list of {@link Resource}s used by the job.
   * @param index             the discretized time index.
   * @param containerMemAlloc the multi-dimension resource vector allocated to
   *                          one container.
   * @return the multi-dimension resource vector consumed by the job.
   */
  public final long getResourceVector(final RLESparseResourceAllocation skyList,
      final int index, final long containerMemAlloc) {
    return skyList.getCapacityAtTime(index).getMemorySize() / containerMemAlloc;
  }

View on GitHub (pinned to 2add963021)

Solutions

1. Set a positive solver timeInterval value in the resource estimator configuration.

When it happens

Trigger: The solver timeInterval configured for the resource estimator is zero or negative, so the skyline history cannot be sliced into estimation intervals.

Common situations: See trigger scenarios.

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