TheR1sing3un commented on PR #7735: URL: https://github.com/apache/paimon/pull/7735#issuecomment-4350753806
CI failed on a different concurrent test in the same suite — `test_concurrent_blob_writes_with_retry` (`pypaimon/tests/blob_table_test.py:2747`). That test isn't modified by this PR but flakes on GHA under the same root cause this PR addresses (high-concurrency commit contention). Master already configures it with `commit.max-retries=50` + `commit.max-retry-wait=30s`, but the latest run shows 10-way concurrent commits exhausting 50 attempts × 30 s back-off (~25 min) and timing out: `Commit failed after 1286102 millis with 50 retries`. Bumping retries higher just makes each iteration run for ~25 minutes. Root cause is contention density, not retry budget. Pushed `c58c33643` to drop `num_threads` from 10 to 5: the retry path is still exercised end-to-end, but with enough breathing room that all writers drain within the existing retry budget. All assertions reference the `num_threads` variable, so the change adjusts the expected row / snapshot counts automatically. This keeps the PR scope cohesive — both `test_concurrent_writes_with_retry` (reader test) and `test_concurrent_blob_writes_with_retry` (blob test) are now stabilized for GHA load. Ready for re-review. -- 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]
