[HUDI-7581] Add a multi writer test with index updates and cleaning

[codope]

Change Logs

The main issue mentioned in the ticket is already fixed by https://github.com/apache/hudi/pull/11496/files#diff-bba4d3c385b771e0e3d64f12cdd07c89b1ad4d9bde44895a999db058c200b428. This PR adds a test to validate the scenario mentioned in the ticket, which is as follows:

• Writer 1 is performing an index update for a specific commit instant, fetching the latest file slices and their corresponding log files.
• Writer 2 is aggressively cleaning older file slices, including log files that Writer 1 might rely on for the index update.
• If Writer 2 removes file slices or log files before Writer 1 finishes the index update, there is a potential for a FileNotFoundException, blocking Writer 1’s operation.

The issue is fixed in the linked patch as the file system view fetched in the getFileSystemView call is always fresh, instead of the one that was computed when HoodieBackedTableMetadataWriter was initialized, meaning Writer 1 should have an up-to-date view of the latest file slices and not face a FileNotFoundException.

Impact

Test a multi writer scenario with index update.

Risk level (write none, low medium or high below)

none

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 to make
  changes to the website.

Contributor's checklist

• Read through contributor's guide
• Change Logs and Impact were stated clearly
• Adequate tests were added if applicable
• CI passed

[yihua]

Could you report the time taken of the new tests added, locally and in CI (see test time breakdown)?

[codope]

Could you report the time taken of the new tests added, locally and in CI (see test time breakdown)?

It takes about 10s locally. Similarly, in CI, it took 11.6s (59th in top 100 long-running test cases) - https://dev.azure.com/apachehudi/hudi-oss-ci/_build/results?buildId=836&view=logs&j=600e7de6-e133-5e69-e615-50ee129b3c08&t=51208f5c-c7eb-5cf4-055e-6966e7c28e33&l=59

[hudi-bot]

CI report:

• 0480cc7 Azure: SUCCESS

Bot commands

@hudi-bot supports the following commands:

• @hudi-bot run azure re-run the last Azure build

[yihua]

LGTM

[yihua]

integration-tests failure is irrelevant. Merging this PR.