kbuci opened a new pull request, #18012:
URL: https://github.com/apache/hudi/pull/18012

   ### Describe the issue this Pull Request addresses
   
   Updated compact to start a heartbeat (within a transaction) before 
attempting to execute a plan. If multiple writers attempt to execute same 
compact/logcompact plan at same time, only one of them will process and the 
rest will fail with an exception (upon seeing a heartbeat has already been 
started) and will abort.
   
   ### Summary and Changelog
   
   Without this change, if multiple jobs are launched at the same that target 
executing the same compact plan (due to a non-HUDI related user-side 
configuration/orchestration issue) then one job can execute the compact plan 
and create an inflight/commit instant file while the other jobs can roll it 
back (and delete inflight instant files or data files). This can lead to 
timeline being in a corrupted state.
   
   ### Impact
   
   <!-- Describe any public API or user-facing feature change or any 
performance impact. -->
   
   ### Risk Level
   
   <!-- Accepted values: none, low, medium or high. Other than `none`, explain 
the risk.
        If medium or high, explain what verification was done to mitigate the 
risks. -->
   
   ### Documentation Update
   
   <!-- Describe any necessary documentation update if there is any new 
feature, config, or user-facing change. If not, put "none".
   
   - The config description must be updated if new configs are added or the 
default value of the configs are changed.
   - Any new feature or user-facing change requires updating the Hudi website. 
Please follow the 
     [instruction](https://hudi.apache.org/contribute/developer-setup#website) 
to make changes to the website. -->
   
   ### Contributor's checklist
   
   - [ ] Read through [contributor's 
guide](https://hudi.apache.org/contribute/how-to-contribute)
   - [ ] Enough context is provided in the sections above
   - [ ] Adequate tests were added if applicable
   


-- 
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]

Reply via email to