nsivabalan commented on issue #17879:
URL: https://github.com/apache/hudi/issues/17879#issuecomment-3881384507
gotcha.
To summarize, here are the diff requirements we have around table service
orchestration and deployment:
- Compaction
R1: Only one TS writer should be able to execute a given compaction plan.
-> Emit heart beats during execution.
- Clustering
R1: Only one TS writer should be able to execute a given clustering plan.
-> Emit heart beats during execution.
R2: Only one TS writer should be able to perform both planning and
execution. If execution fails after planning for any reason, the plan should be
cleaned up by some TS writer after some threshold.
-> Concurrent writer or TS planner could hit FileNotFound issue if not
for abort state.
-> Abort state or go w/ inflight deletion/nuking of plans.
Let me know if this is right
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
