Describe the problem you faced
we are using flink compaction async.
sometimes, the same file group compact task will be distributed to different task manager even though the compaction plan distribute the compact task using keyby filegroupid(hudi-4397),
this will lead to the exception:
The file being written is in an invalid state. Probably caused by an error thrown previously. Current state: COLUMN
To Reproduce
Steps to reproduce the behavior:
- job manager is killed and restart
2.all task managers register again
3.say task manager1 will be assigned different file group id compact task, which maybe distribute to task manager2 before task manager re-register
i noticed that, when task manager re-registered, the compact task will continue to run which started before this re-register happened
Environment Description