Re: Discussing negative acknowledgment in batch default behavior

2022-05-22 Thread Asaf Mesika
Resurfacing this as it seems (to me) an important correction to be made.

Would love your opinions on this.

Thanks!

Asaf

On Wed, May 11, 2022 at 1:16 PM Asaf Mesika  wrote:

> Hello all,
>
> I have a question regarding a feature introduced in 2.6.0 called Negative
> Acknowledgement in Batch Level index, described in PIP-54
> 
> .
>
> In short: Before this feature, if you would write in batches (in producer)
> to Pulsar (which makes sense most would for performance reasons), then a
> consumer sending a negative acknowledgment for 1 message in the batch (say
> we have 500 in a single batch), would cause the consumer to get the all
> messages in the batch (500) redelivered as if they were not acknowledge.
>
> PIP-54 fixes that by keeping the ack per message in a batch using a bitmap
> index. The caveats are more memory consumption since the broker keeps those
> bitmaps in-memory for any inflight batch.
>
> With PIP-54 Pulsar IMO becomes "complete" in that it acts the way you
> would expect it to be, in normal circumstances (as opposed to disconnects,
> machine crashing, etc).
>
> This feature was introduced in 2.6.0, roughly 2 years ago, and is off by
> default.
>
> I was wondering what the developers community thoughts on turning it on by
> default? Has anyone experienced any performance degradation to it? Have you
> turned it on in your clusters?
>
> Thanks a lot for your time.
>
> Asaf Mesika
>


[GitHub] [pulsar-site] urfreespace commented on pull request #90: Make Algolia DocSearch configuration simple

2022-05-22 Thread GitBox


urfreespace commented on PR #90:
URL: https://github.com/apache/pulsar-site/pull/90#issuecomment-1134084279

   thanks a lot for @dave2wave 


-- 
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: dev-unsubscr...@pulsar.apache.org

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



[GitHub] [pulsar-site] urfreespace merged pull request #90: Make Algolia DocSearch configuration simple

2022-05-22 Thread GitBox


urfreespace merged PR #90:
URL: https://github.com/apache/pulsar-site/pull/90


-- 
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: dev-unsubscr...@pulsar.apache.org

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



Re: [DISCUSS] Apache Pulsar 2.10.1 release

2022-05-22 Thread Hang Chen
+1

There are a lot of transaction fixes.

Thanks,
Hang

PengHui Li  于2022年5月21日周六 13:06写道:
>
> Hello, Pulsar community:
>
> I'd like to propose to release Apache Pulsar 2.10.1
>
> Currently, we have 190 commits [0] and there are many transaction
> fixes, security fixes.
>
> And there are 22 open PRs [1], I will follow them to make sure that
> the important fixes could be contained in 2.10.1
>
> If you have any important fixes or any questions,
> please reply to this email, we will evaluate whether to
> include it in 2.10.1
>
> [0]
> https://github.com/apache/pulsar/pulls?q=is%3Amerged+is%3Apr+label%3Arelease%2F2.10.1+
> [1]
> https://github.com/apache/pulsar/pulls?q=is%3Aopen+is%3Apr+label%3Arelease%2F2.10.1+
>
> Best Regards
> Penghui


[GitHub] [pulsar-client-node] massakam commented on pull request #215: prevent double callback segfault in client close

2022-05-22 Thread GitBox


massakam commented on PR #215:
URL: 
https://github.com/apache/pulsar-client-node/pull/215#issuecomment-1134166187

   If https://github.com/apache/pulsar/pull/15508 fundamentally solves this 
issue, I think it's enough to raise the minimum version of the C++ client 
required by the Node.js client by the next release. I don't think it's 
necessary to merge this workaround.


-- 
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: dev-unsubscr...@pulsar.apache.org

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