Jason-liujc opened a new issue, #9728:
URL: https://github.com/apache/hudi/issues/9728

   **_Tips before filing an issue_**
   
   - Have you gone through our [FAQs](https://hudi.apache.org/learn/faq/)?
   
   - Join the mailing list to engage in conversations and get faster support at 
[email protected].
   
   - If you have triaged this as a bug, then file an 
[issue](https://issues.apache.org/jira/projects/HUDI/issues) directly.
   
   **Describe the problem you faced**
   
   We have a usecase where might have a lot of concurrent writes to the same 
partition under special scenarios. We are testing if Hudi supports this 
natively by changing some of the lock retry/wait-time parameters. 
   We are trying allow all these writers to go through with optimistic retries 
eventually by using really high `num_retries` and `wait_time_ms` parameters.
   
   **To Reproduce**
   
   We have the following using options related to concurrency control:
   
   ```
         "hoodie.write.concurrency.mode" -> "optimistic_concurrency_control",
         "hoodie.write.lock.client.wait_time_ms_between_retry" -> "60000",
         "hoodie.write.lock.max_wait_time_ms_between_retry" -> "600000",
         "hoodie.write.lock.num_retries" -> "60",
         "hoodie.write.lock.wait_time_ms" -> "360000",
         "hoodie.write.lock.wait_time_ms_between_retry" -> "360000",
         "hoodie.cleaner.policy.failed.writes" -> "LAZY"
   ```
   
   We spinned up 7 jobs that writes to the same table. Each job should take 
around ~20 minutes to finish on its own.
   
   **Expected behavior**
   
   These 7 jobs will have conflicting writes and will retry and will succeed 
eventually.
   
   Base on the retry parameters I have set, I'd expect it to run for at least 4 
hours.
   
   **Environment Description**
   
   * Hudi version : 0.13.0
   
   * Spark version : 3.3
   
   * Hive version : 3.1.3
   
   * Hadoop version : 3.3.3
   
   * Storage (HDFS/S3/GCS..) : S3
   
   * Running on Docker? (yes/no) : no
   
   
   **Additional context**
   
   Running these workloads on EMR. This is a follow up to this issue: 
https://github.com/apache/hudi/issues/9512
   
   **Stacktrace**
   
   Seeing these errors after 1.2 hours for 40% of the jobs:
   
   ```
   java.util.ConcurrentModificationException: Cannot resolve conflicts for 
overlapping writes
        at 
org.apache.hudi.client.transaction.SimpleConcurrentFileWritesConflictResolutionStrategy.resolveConflict(SimpleConcurrentFileWritesConflictResolutionStrategy.java:108)
        at 
org.apache.hudi.client.utils.TransactionUtils.lambda$resolveWriteConflictIfAny$0(TransactionUtils.java:85)
        at 
java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1384)
        at 
java.util.stream.Streams$ConcatSpliterator.forEachRemaining(Streams.java:742)
        at 
java.util.stream.Streams$ConcatSpliterator.forEachRemaining(Streams.java:742)
        at 
java.util.stream.ReferencePipeline$Head.forEach(ReferencePipeline.java:647)
   ```
   
   


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