[GitHub] [pulsar] Anonymitaet commented on a diff in pull request #17535: [feature][blog] Add 2.7.5 Release Blog

[GitBox <gi...@apache.org>]

Anonymitaet commented on code in PR #17535:
URL: https://github.com/apache/pulsar/pull/17535#discussion_r965585225


##########
site2/website/blog/2022-09-09-Apache-Pulsar-2-7-5.md:
##########
@@ -0,0 +1,63 @@
+---
+title: "What’s New in Apache Pulsar 2.7.5"
+date: 2022-09-09
+author: "Jason918, momo-jun"
+---
+
+The Apache Pulsar community releases version 2.7.5! 23 contributors provided improvements and bug fixes that delivered 89 commits. Thanks for all your contributions.
+
+The highlight of the 2.7.5 release is that it fixes some critical bugs on broker, proxy, and storage, including message/data loss, broker deadlock, and connection leak. Note that 2.7.5 is the last release of 2.7.x.
+
+This blog walks through the most noteworthy changes. For the complete list, including all feature enhancements and bug fixes, check out the [Pulsar 2.7.5 Release Notes](https://pulsar.apache.org/release-notes/versioned/pulsar-2.7.5/).
+
+### Fixed the deadlock on metadata cache missing while checking replications. [PR-16889](https://github.com/apache/pulsar/pull/16889)
+
+#### Issue
+After the changes in [#12340](https://github.com/apache/pulsar/pull/12340), there are still a couple of places making blocking calls. These calls occupy all the ordered scheduler threads preventing the callbacks from completing until the 30 seconds timeout expires.
+
+#### Resolution
+Change the blocking calls to async mode on the metadata callback thread.
+
+
+### Fixed the deadlock when using the key_shared mode. [PR-11965](https://github.com/apache/pulsar/pull/11965)
+
+#### Issue
+When the key_shared mode is used in consumers, deadlock may happen in the broker due to some race conditions and result in a lot of `CLOSE_WAIT` status connections.
+
+#### Resolution
+Change unlock before the callback in the `asyncDelete` function of `ManagedCursorImpl`.
+
+### Fixed the message loss issue due to ledger rollover. [PR-14703](https://github.com/apache/pulsar/pull/14703)
+
+#### Issue
+If users config `managedLedgerMaxLedgerRolloverTimeMinutes > 0`, and the rollover happens when the ManagedLedger state is `CreatingLedger`, the messages written during that time are lost.
+
+#### Resolution
+Rollover only when the ledger state is ``LedgerOpened`. 

Review Comment:
   ```suggestion
   Rollover only when the ledger state is `LedgerOpened`. 
   ```



-- 
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: commits-unsubscribe@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org