wolfstudy commented on a change in pull request #7756: URL: https://github.com/apache/pulsar/pull/7756#discussion_r472066961
########## File path: site2/website/blog/2020-08-17-Apache-Pulsar-2-6-1.md ########## @@ -0,0 +1,295 @@ +--- +author: XiaoLong Ran +authorURL: https://twitter.com/wolf4j1 +title: Apache Pulsar 2.6.1 +--- +We are very glad to see the Apache Pulsar community has successfully released the wonderful 2.6.1 version after accumulated hard work. It is a great milestone for this fast-growing project and the whole Pulsar community. This is the result of a huge effort from the community, with over 90 commits and a long list of improvements and bug fixes. + +Here is a selection of some of the most interesting and major features added to Pulsar 2.6.1. + +<!--truncate--> + +## Broker + +#### Limit the batch size to the minimum of the `maxNumberOfMessages` and `maxSizeOfMessages` + +The Batch size is not limited to the minimum of the `maxNumberOfMessages` and `maxSizeOfMessages` from the `BatchReceive` policy. + +1. Batch size is not limited to the minimum of the maxNumberOfMessages and maxSizeOfMessages from the BatchReceive policy. +2. When the batch size is greater than the receiveQ of the consumer (I used a batch size of 3000 and a receiveQ of 500), I notice the following issues: + + In a multi-topic (pattern) consumer, the client stops receiving any messages. I think it gets paused and never resumed when setting a timeout in the batch policy. Only one batch is fetched and the client is never resumed. + +For more information about implementation details, see [PR-6865](https://github.com/apache/pulsar/pull/6865). + +#### Fix hash range conflict issue in Key_Shared subscription with sticky hash range +In `Key_Shared` subscription where the`stickyHashRange` is used, consumers are not allowed to use interleaving hashes. Review comment: What is difference? ---------------------------------------------------------------- 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: [email protected]
