+1 (non-binding)
Thanks for driving this helpful proposal!
Best,
Max Xu
On Wed, May 10, 2023 at 6:52 PM Asaf Mesika wrote:
> Hi,
>
> I'm starting the vote process for PIP-265.
>
> Link: https://github.com/apache/pulsar/issues/20207
>
> Thanks!
>
> Asaf
>
+1 (binding)
It will be helpful for PR review.
Best,
Hang
PengHui Li 于2023年5月15日周一 10:09写道：
>
> +1 (binding)
>
> Thanks,
> Penghui
>
> On Wed, May 10, 2023 at 6:52 PM Asaf Mesika wrote:
>
> > Hi,
> >
> > I'm starting the vote process for PIP-265.
> >
> > Link: https://github.com/apache/pulsar/
+1 (binding)
Thanks,
Penghui
On Wed, May 10, 2023 at 6:52 PM Asaf Mesika wrote:
> Hi,
>
> I'm starting the vote process for PIP-265.
>
> Link: https://github.com/apache/pulsar/issues/20207
>
> Thanks!
>
> Asaf
>
There are multiple factors tcp would be better than http when you are
considering performance and scale due to lower overhead, faster parsing,
more control over connection, congestion control, etc and that could be
reasons why we have tcp binary protocol for producers/consumers
communication with s
> On May 10, 2023, at 1:01 AM, Asaf Mesika wrote:
>
> On Tue, May 9, 2023 at 11:29 PM Dave Fisher wrote:
>
>>
>>
On May 8, 2023, at 2:49 AM, Asaf Mesika wrote:
>>>
>>> Your feedback made me realized I need to add "TL;DR" section, which I
>> just
>>> added.
>>>
>>> I'm quoting it h
Bumping, as I have received only 1 partial feedback so far on the PIP.
Any feedback is highly appreciated!
Thanks!
Asaf
On Wed, May 10, 2023 at 11:00 AM Asaf Mesika wrote:
>
>
> On Tue, May 9, 2023 at 11:29 PM Dave Fisher wrote:
>
>>
>>
>> > On May 8, 2023, at 2:49 AM, Asaf Mesika wrote:
>>
If I dive into the exact details of the cause of the
performance implications in current Admin HTTP API:
Do you think the root cause of the performance is the Jersey implementation
of `AsyncResponse.resume(stats)` which takes a thread from a thread pool,
serialize the object and then performs a bl
Hi -
I have not looked at all your links but I think this is a great idea. This will
help everyone pay attention better.
Best,
Dave
Sent from my iPhone
> On May 14, 2023, at 12:33 AM, tison wrote:
>
> Of course, changing the workflow cannot magically increase the bandwidth to
> handle stale
Of course, changing the workflow cannot magically increase the bandwidth to
handle stale issues. That is what the triage guide wants to encourage
committers to practice. But such a move can reduce the frustrating
experience and explicitly express who is responsible for taking the next
action to nud
Hi devs,
Recently, I have handled a large number of stale issues and noticed that
periodically notifying users that "the issue is stale" without any human
reaction can be a frustrating experience, e.g., ISSUE-13925[1].
Learning from the INFRA JIRA project experience, I propose we replace the
stal
10 matches
Mail list logo
