Denovo1998 opened a new pull request, #24620:
URL: https://github.com/apache/pulsar/pull/24620

   <!--
   ### Contribution Checklist
     - PR title format should be *[type][component] summary*. For details, see 
*[Guideline - Pulsar PR Naming 
Convention](https://pulsar.apache.org/contribute/develop-semantic-title/)*. 
     - Fill out the template below to describe the changes contributed by the 
pull request. That will give reviewers the context they need to do the review.
     - Each pull request should address only one issue, not mix up code from 
multiple issues.
     - Each commit in the pull request has a meaningful commit message
     - Once all items of the checklist are addressed, remove the above text and 
this checklist, leaving only the filled out template below.
   -->
   <!-- Either this PR fixes an issue, -->
   Fixes #xyz
   <!-- or this PR is one task of an issue -->
   Main Issue: #xyz
   <!-- If the PR belongs to a PIP, please add the PIP link here -->
   PIP: #xyz 
   <!-- Details of when a PIP is required and how the PIP process work, please 
see: https://github.com/apache/pulsar/blob/master/pip/README.md -->
   ### Motivation
   Fixed race conditions in thread safety tests that were causing intermittent 
IllegalReferenceCountException failures due to improper resource cleanup order 
and unrealistic concurrent write patterns.
   ### Modifications
   1. Enhanced Thread Safety Test Design
   - Fixed concurrent write race condition: Changed 
testConcurrentContainsMessageWithWrites from concurrent writes to sequential 
writes with concurrent reads, matching real-world
   usage patterns where addMessage is called sequentially
   - Improved test structure: Single writer thread generates sequential 
ledgerIds (1000, 1001, 1002...) while multiple reader threads concurrently call 
containsMessage()
   - Added proper error handling: Enhanced exception tracking and reporting 
with detailed logging
   2. Fixed Resource Cleanup Race Condition
   - Resolved IllegalReferenceCountException: Fixed tearDown method to shutdown 
ExecutorService before closing tracker, preventing threads from accessing 
released Netty ByteBufs
   - Improved cleanup order: Ensures all background threads are terminated 
before releasing resources
   ### Verifying this change
   - [x] Make sure that the change passes the CI checks.
   *(Please pick either of the following options)*
   This change is a trivial rework / code cleanup without any test coverage.
   *(or)*
   This change is already covered by existing tests, such as *(please describe 
tests)*.
   *(or)*
   This change added tests and can be verified as follows:
   *(example:)*
     - *Added integration tests for end-to-end deployment with large payloads 
(10MB)*
     - *Extended integration test for recovery after broker failure*
   ### Does this pull request potentially affect one of the following parts:
   <!-- DO NOT REMOVE THIS SECTION. CHECK THE PROPER BOX ONLY. -->
   *If the box was checked, please highlight the changes*
   - [ ] Dependencies (add or upgrade a dependency)
   - [ ] The public API
   - [ ] The schema
   - [ ] The default values of configurations
   - [ ] The threading model
   - [ ] The binary protocol
   - [ ] The REST endpoints
   - [ ] The admin CLI options
   - [ ] The metrics
   - [ ] Anything that affects deployment
   ### Documentation
   <!-- DO NOT REMOVE THIS SECTION. CHECK THE PROPER BOX ONLY. -->
   - [ ] `doc` <!-- Your PR contains doc changes. -->
   - [ ] `doc-required` <!-- Your PR changes impact docs and you will update 
later -->
   - [ ] `doc-not-needed` <!-- Your PR changes do not impact docs -->
   - [ ] `doc-complete` <!-- Docs have been already added -->
   ### Matching PR in forked repository
   PR in forked repository: <!-- ENTER URL HERE -->
   <!--
   After opening this PR, the build in apache/pulsar will fail and instructions 
will
   be provided for opening a PR in the PR author's forked repository.
   apache/pulsar pull requests should be first tested in your own fork since 
the 
   apache/pulsar CI based on GitHub Actions has constrained resources and quota.
   GitHub Actions provides separate quota for pull requests that are executed 
in 
   a forked repository.
   The tests will be run in the forked repository until all PR review comments 
have
   been handled, the tests pass and the PR is approved by a reviewer.
   -->
   


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