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

   …flaky tests (#68)
   
   ### Change Logs
   
   Followup PR for: https://github.com/apache/hudi/pull/13787
   
   Our current index are loaded asynchronously. If it fails to load in 1s, it 
will fallback doing a full load so as to not block split generation. When 
testing for correctness in our tests, we require indexes to be loaded fully. If 
the server that is running the test is busy or overloaded, it will increase the 
likelihood of the test failing.
   
   While this is not a permanent fix, it should reduce the probability of tests 
failing. The permanent fix should be adding a synchronous flag so that index 
metadata is loaded synchronously to remove these timing issues entirely.
   
   ### Impact
   
   Reduce probability of async metadata tests failing.
   
   ### Risk level (write none, low medium or high below)
   
   Low
   
   ### 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