apache/seatunnel · warning

Post-sync operation failed and will be retried: action={}, s

Error message

Post-sync operation failed and will be retried: action={}, splitId={}, source={}, retryCount={}

What it means

Within commitSingleOperation, any exception thrown while committing a post-sync operation (backup via commitBackupOperation or other actions) is caught, logged as this warning with the action, splitId, sanitized source path, and retry count, and the method returns FAILED_RETRYABLE. The operation will be retried on subsequent commit passes; repeated failures increment retryCount.

Source

Thrown at seatunnel-connectors-v2/connector-file/connector-file-base/src/main/java/org/apache/seatunnel/connectors/seatunnel/file/source/split/ContinuousMultipleTableFileSourceSplitEnumerator.java:716

        Optional<TableScanContext> tableContextOpt = findTableScanContext(op.getTableId());
        if (!tableContextOpt.isPresent()) {
            log.warn(
                    "Post-sync operation failed: table context not found, tableId={}, splitId={}",
                    op.getTableId(),
                    op.getSplitId());
            return OpCommitResult.FAILED_RETRYABLE;
        }

        try {
            if (op.getAction() == FilePostSyncAction.DELETE) {
                return commitDeleteOperation(tableContextOpt.get(), op, checkpointId);
            }
            if (op.getAction() == FilePostSyncAction.BACKUP) {
                return commitBackupOperation(tableContextOpt.get(), op, checkpointId);
            }
            return OpCommitResult.SUCCESS;
        } catch (Exception e) {
            log.warn(
                    "Post-sync operation failed and will be retried: action={}, splitId={}, source={}, retryCount={}",
                    op.getAction(),
                    op.getSplitId(),
                    maskUriUserInfo(op.getSourcePath()),
                    op.getRetryCount(),
                    e);
            return OpCommitResult.FAILED_RETRYABLE;
        }
    }

    private OpCommitResult commitDeleteOperation(
            TableScanContext ctx, FileSourceOperationState op, long checkpointId)
            throws IOException {
        String trashPath = buildDeleteStagingPath(op, checkpointId);
        FileStatus trashedStatus = getFileStatusIfPresent(ctx.sourceFs, trashPath);
        if (trashedStatus == null
                && getFileStatusIfPresent(ctx.sourceFs, op.getSourcePath()) == null) {
            log.info(

View on GitHub (pinned to cf67b549a7)

Solutions

1. Read the logged cause to identify the filesystem failure and fix it (connectivity, permissions, disk space)
2. Verify both source and target paths exist and are writable by the job user
3. Monitor retryCount — if it keeps growing, the operation will never succeed without fixing the underlying error

// Pre-check source and target writability before queuing the backup action
if (!fs.exists(targetDir)) {
    throw new IllegalStateException("Backup target dir missing: " + targetDir);
}
if (!fs.getFileStatus(sourcePath).isFile()) {
    throw new IllegalStateException("Backup source missing: " + sourcePath);
}

try {
    return commitBackupOperation(tableContextOpt.get(), op, checkpointId);
} catch (Exception e) {
    log.warn("Post-sync operation failed and will be retried: action={}, splitId={}, source={}, retryCount={}",
            op.getAction(), op.getSplitId(), maskUriUserInfo(op.getSourcePath()),
            op.getRetryCount(), e);
    return OpCommitResult.FAILED_RETRYABLE;
}

When it happens

Trigger: commitBackupOperation (or another action handler) throws — filesystem rename/copy failures, source or target path temporarily missing, permission errors, network failures against HDFS/S3 during the post-sync write.

Common situations: Target directory unavailable or full during backup; transient S3/HDFS errors; permissions changed on the sync target; source file already moved by an external process.

Understand the failure class

Background: "failed to write file", "Could not save figure", "Error saving remote file" — file write failed: causes and fixes across languages and libraries — this error's family across 38 libraries.

Related errors

• Continuous discovery scan failed, will retry in next interva
• Post-sync delete: rename-to-trash failed, will retry: source
• Skip post-sync staging because table context is not found. s
• Failed to evaluate recovered split {}, re-enqueue it conserv
• Post-sync operation failed: table context not found, tableId

AI-assisted analysis of apache/seatunnel@cf67b549a7 (2026-09-10). Data as JSON: /api/errors/eb2f4aec3f3eeac2. Report an issue: GitHub.