the-other-tim-brown opened a new pull request, #13399:
URL: https://github.com/apache/hudi/pull/13399

   ### Change Logs
   
   The marker handler only uses the engine context for listing and deleting 
files. The directories managed only have a single level and manage a relatively 
small number of files so using a distributed engine to list or delete files is 
overkill. In spark, the executors will ask the timeline server to create 
markers for the files being created which in turn will launch more spark tasks 
if the spark engine context is used. If the cluster does not have capacity for 
more tasks, this can lead to a deadlock.
   
   While looking through the code, there were other small opportunities for 
improvement in the handler code that are added to this PR.
   
   ### Impact
   
   Improve performance of remote markers
   
   ### Risk level (write none, low medium or high below)
   
   _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 create a Jira ticket, attach the
     ticket number here and 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)
   - [ ] Change Logs and Impact were stated clearly
   - [ ] Adequate tests were added if applicable
   - [ ] CI passed
   


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