apache/iceberg · error · IllegalArgumentException

Invalid operator event type:

Error message

Invalid operator event type: 

What it means

TriggerManagerOperator.handleOperatorEvent() only processes LockReleaseEvent sent from its coordinator. Any other OperatorEvent type indicates a protocol mismatch between coordinator and operator, so it throws IllegalArgumentException with the event's class name.

Source

Thrown at flink/v2.3/flink/src/main/java/org/apache/iceberg/flink/maintenance/operator/TriggerManagerOperator.java:219

      nextEvaluationTimeState.add(nextEvaluationTime);
    }

    accumulatedChangesState.update(accumulatedChanges);
    lastTriggerTimesState.update(lastTriggerTimes);
    LOG.info(
        "Storing state: nextEvaluationTime {}, accumulatedChanges {}, lastTriggerTimes {}",
        nextEvaluationTime,
        accumulatedChanges,
        lastTriggerTimes);
  }

  @Override
  public void handleOperatorEvent(OperatorEvent event) {
    if (event instanceof LockReleaseEvent) {
      LOG.info("Received lock released event: {}", event);
      handleLockRelease((LockReleaseEvent) event);
    } else {
      throw new IllegalArgumentException(
          "Invalid operator event type: " + event.getClass().getCanonicalName());
    }
  }

  @Override
  public void processElement(StreamRecord<TableChange> streamRecord) throws Exception {
    TableChange change = streamRecord.getValue();
    accumulatedChanges.forEach(tableChange -> tableChange.merge(change));
    if (nextEvaluationTime == null) {
      checkAndFire(getProcessingTimeService());
    } else {
      LOG.info(
          "Trigger manager rate limiter triggered current: {}, next: {}, accumulated changes: {},{}",
          getProcessingTimeService().getCurrentProcessingTime(),
          nextEvaluationTime,
          accumulatedChanges,
          maintenanceTaskNames);
      rateLimiterTriggeredCounter.inc();

View on GitHub (pinned to 86d9c8fc54)

Solutions

1. Verify the coordinator paired with this operator only sends LockReleaseEvent
2. Align Iceberg versions across all job vertices (avoid partial upgrades / mixed classpath)
3. Check that the job was not restored from a savepoint produced by an incompatible version
4. If new event types are needed, add instanceof branches to handleOperatorEvent

Example fix

// before
operator.handleOperatorEvent(new LockRegisterEvent(factory, id)); // IllegalArgumentException
// after
coordinatorContext.sendOperatorEvent(new LockReleaseEvent(id));

// before invoking the operator's event handler
if (!(event instanceof LockReleaseEvent)) {
  throw new IllegalArgumentException("TriggerManagerOperator only accepts LockReleaseEvent, got " + event.getClass());
}

if (event instanceof LockReleaseEvent release) {
  operator.handleOperatorEvent(release);
} else { /* route to the right operator */ }

try {
  operator.handleOperatorEvent(event);
} catch (IllegalArgumentException e) {
  LOG.error("Coordinator sent unsupported OperatorEvent to TriggerManagerOperator", e);
  throw e;
}

When it happens

Trigger: The TriggerManagerCoordinator sends an event type other than LockReleaseEvent (e.g. LockRegisterEvent) to this operator; custom code invokes handleOperatorEvent with a foreign OperatorEvent.

Common situations: Mismatched coordinator/operator versions after a savepoint restore or partial upgrade; custom operators reusing this operator's event gateway; tests invoking handleOperatorEvent with wrong event instances.

Understand the failure class

Background: "Must be a positive integer", "Invalid value", "Unsupported": the invalid-argument-value error family, when a library rejects the value you pass — this error's family across 35 libraries.

Related errors

• Received unknown event from subtask %d: %s
• Invalid operator event type:
• Invalid operator event type:
• Invalid operator event type:
• Invalid operator event type:

AI-assisted analysis of apache/iceberg@86d9c8fc54 (2026-09-12). Data as JSON: /api/errors/842620d891c3264c. Report an issue: GitHub.