[jira] [Commented] (KAFKA-9838) Add additional log concurrency test cases

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/KAFKA-9838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17082753#comment-17082753 ] 

ASF GitHub Bot commented on KAFKA-9838:
---------------------------------------

hachikuji commented on pull request #8476: KAFKA-9838; Add log concurrency test and fix minor race condition
URL: https://github.com/apache/kafka/pull/8476
 
 
   The patch adds a new test case for validating concurrent read/write behavior in the `Log` implementation. In the process of verifying this, we found a race condition in `read`. The previous logic checks whether the start offset is equal to the end offset before collecting the high watermark. It is possible that the log is truncated in between these two conditions which could cause the high watermark to be equal to the log end offset. When this happens, `LogSegment.read` fails because it is unable to find the starting position to read from.
   
   ### Committer Checklist (excluded from commit message)
   - [ ] Verify design and implementation 
   - [ ] Verify test coverage and CI build status
   - [ ] Verify documentation (including upgrade notes)
   
 
----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> Add additional log concurrency test cases
> -----------------------------------------
>
>                 Key: KAFKA-9838
>                 URL: https://issues.apache.org/jira/browse/KAFKA-9838
>             Project: Kafka
>          Issue Type: Improvement
>            Reporter: Jason Gustafson
>            Assignee: Jason Gustafson
>            Priority: Major
>
> A couple recent bug fixes affecting log read semantics were due to race conditions with concurrent operations: see KAFKA-9807 and KAFKA-9835. We need better testing of concurrent operations on the log to know if there are additional problems and to prevent future regressions.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)