Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] [Zeta] Cancelled 323 tasks, only 24 were successfully cancelled; the rest remain in Cancelling state. #7369

Closed
2 of 3 tasks
xiaohundun opened this issue Aug 12, 2024 · 1 comment
Labels

Comments

@xiaohundun
Copy link

xiaohundun commented Aug 12, 2024

Search before asking

  • I had searched in the issues and found no similar issues.

What happened

Cancelled 323 tasks, only 24 were successfully cancelled; the rest remain in Cancelling state.

Deploy SeaTunnel Engine In Separated Cluster Mode

SeaTunnel Version

2.3.6

SeaTunnel Config

seatunnel:
  engine:
    classloader-cache-mode: true
    history-job-expire-minutes: 1440
    backup-count: 1
    queue-type: blockingqueue
    print-execution-info-interval: 60
    print-job-metrics-info-interval: 60
    slot-service:
      dynamic-slot: true
    checkpoint:
      interval: 300000
      timeout: 60000
      storage:
        type: hdfs
        max-retained: 3
        plugin-config:
          namespace: /tmp/seatunnel/checkpoint_snapshot
          storage.type: hdfs
          fs.defaultFS: file:///tmp/ # Ensure that the directory has written permission

Running Command

http://**:5801/hazelcast/rest/maps/stop-job

Error Exception

There are no errors in the log file, only some warnings.

2024-08-12 08:58:50,953 INFO  [o.a.s.e.s.TaskExecutionService] [hz.main.seaTunnel.task.thread-307] - [localhost]:5802 [seatunnel] [5.1] Task TaskGroupLocation{jobId=874174348949454849, pipelineId=1, taskGroupId=1} complete with state CANCELED
2024-08-12 08:58:51,006 WARN  [o.a.s.e.s.TaskExecutionService] [BlockingWorker-TaskGroupLocation{jobId=874174348949848065, pipelineId=1, taskGroupId=1}] - [localhost]:5802 [seatunnel] [5.1] try lock failed in update metrics
2024-08-12 08:58:51,058 WARN  [o.a.s.e.s.TaskExecutionService] [BlockingWorker-TaskGroupLocation{jobId=874174348950044673, pipelineId=1, taskGroupId=30000}] - [localhost]:5802 [seatunnel] [5.1] try lock failed in update metrics
2024-08-12 08:58:51,058 INFO  [o.a.s.e.s.TaskExecutionService] [BlockingWorker-TaskGroupLocation{jobId=874174348950044673, pipelineId=1, taskGroupId=1}] - [localhost]:5802 [seatunnel] [5.1] taskGroup TaskGroupLocation{jobId=874174348950044673, pipelineId=1, taskGroupId=1} complete with CANCELED
2024-08-12 08:58:51,058 INFO  [.e.IncrementalSourceEnumerator] [BlockingWorker-TaskGroupLocation{jobId=874174348950044673, pipelineId=1, taskGroupId=1}] - Closing enumerator...
2024-08-12 08:58:51,058 INFO  [o.a.s.e.s.TaskExecutionService] [hz.main.seaTunnel.task.thread-309] - [localhost]:5802 [seatunnel] [5.1] Task TaskGroupLocation{jobId=874174348950044673, pipelineId=1, taskGroupId=1} complete with state CANCELED
2024-08-12 08:58:51,106 WARN  [o.a.s.e.s.TaskExecutionService] [BlockingWorker-TaskGroupLocation{jobId=874174348950437889, pipelineId=1, taskGroupId=1}] - [localhost]:5802 [seatunnel] [5.1] try lock failed in update metrics
2024-08-12 08:58:51,154 WARN  [o.a.s.e.s.TaskExecutionService] [BlockingWorker-TaskGroupLocation{jobId=874174348950634497, pipelineId=1, taskGroupId=30000}] - [localhost]:5802 [seatunnel] [5.1] try lock failed in update metrics
2024-08-12 08:58:51,204 WARN  [o.a.s.e.s.TaskExecutionService] [BlockingWorker-TaskGroupLocation{jobId=874174348950831105, pipelineId=1, taskGroupId=30000}] - [localhost]:5802 [seatunnel] [5.1] try lock failed in update metrics
2024-08-12 08:58:51,382 WARN  [o.a.s.e.s.TaskExecutionService] [BlockingWorker-TaskGroupLocation{jobId=874174348951617537, pipelineId=1, taskGroupId=30000}] - [localhost]:5802 [seatunnel] [5.1] try lock failed in update metrics

Zeta or Flink or Spark Version

Zeta 2.3.6

Java or Scala Version

openjdk 17.0.10 2024-01-18 LTS

Screenshots

image

Are you willing to submit PR?

  • Yes I am willing to submit a PR!

Code of Conduct

@xiaohundun
Copy link
Author

I see that this issue has already been fixed in the dev branch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant