hangc0276 opened a new pull request, #4830:
URL: https://github.com/apache/bookkeeper/pull/4830

   …ENTRY_REQUEST p99 latency spike (#4730)"
   
   This reverts commit 8664dd962935dc23d40218f1bf228661776580fd.
   
   Descriptions of the changes in this PR:
   
   <!-- Either this PR fixes an issue, -->
   
   Fix #xyz
   
   <!-- or this PR is one task of an issue -->
   
   Main Issue: #xyz
   
   <!-- If the PR belongs to a BP, please add the BP link here -->
   
   BP: #xyz
   
   ### Motivation
   
   Revert the PR https://github.com/apache/bookkeeper/pull/4730 due to the 
deadlock: https://github.com/apache/bookkeeper/pull/4730#issuecomment-4878839966
   
   ### Changes
   
   (Describe: what changes you have made)
   
   > ---
   > In order to uphold a high standard for quality for code contributions, 
Apache BookKeeper runs various precommit
   > checks for pull requests. A pull request can only be merged when it passes 
precommit checks.
   >
   > ---
   > Be sure to do all the following to help us incorporate your contribution
   > quickly and easily:
   >
   > If this PR is a BookKeeper Proposal (BP):
   >
   > - [ ] Make sure the PR title is formatted like:
   >     `<BP-#>: Description of bookkeeper proposal`
   >     `e.g. BP-1: 64 bits ledger is support`
   > - [ ] Attach the master issue link in the description of this PR.
   > - [ ] Attach the google doc link if the BP is written in Google Doc.
   >
   > Otherwise:
   > 
   > - [ ] Make sure the PR title is formatted like:
   >     `<Issue #>: Description of pull request`
   >     `e.g. Issue 123: Description ...`
   > - [ ] Make sure tests pass via `mvn clean apache-rat:check install 
spotbugs:check`.
   > - [ ] Replace `<Issue #>` in the title with the actual Issue number.
   > 
   > ---
   


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