Thanks for your information!
Then I think we can merge PR-16163 to master and release with 2.11, while
not to cherry-pick to <=2.10.
Best,
tison.
Ran Gao 于2022年6月23日周四 10:01写道：
> One problem is that the presto 334 needs jdk11+ and it didn't support
> jdk8, maybe 2.11 is a good time for
Hi Michael,
Thanks for your feedback.
> I define a client's primary cluster as "healthy" when it is "healthy"
for all of its producers and consumers. I define a healthy producer as
one that can connect to a topic and publish messages within certain
latency and throughput thresholds (configured
urfreespace merged PR #121:
URL: https://github.com/apache/pulsar-site/pull/121
--
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:
On Jun 21, 2022, at 1:00 AM, Haiting Jiang wrote:
>
> Hi Pulsar community:
>
> I open a pip to discuss "Shadow Topic, an alternative way to support readonly
> topic ownership."
>
> Proposal Link: https://github.com/apache/pulsar/issues/16153
>
> ---
>
> ## Motivation
>
> The motivation
Hi Asaf,
> I did a quick reading and I couldn't understand the gist of this change:
> The shadow topic doesn't really have it's own messages, or it's own ledgers
> right? When it reads messages, it reads from the original topic ledgers. So
> the only thing you need to do is sync the "metadata" -
gaoran10 commented on code in PR #219:
URL: https://github.com/apache/pulsar-client-node/pull/219#discussion_r904458120
##
src/Consumer.cc:
##
@@ -63,7 +63,9 @@ void MessageListenerProxy(Napi::Env env, Napi::Function
jsCallback, MessageListe
Consumer *consumer =
> One question comes to mind here: Why not simply read the ledger information
from original topic, without copy?
I think this is a good idea.
Penghui
On Jun 22, 2022, 23:57 +0800, dev@pulsar.apache.org, wrote:
>
> One question comes to mind here: Why not simply read the ledger information
> from
One problem is that the presto 334 needs jdk11+ and it didn't support jdk8,
maybe 2.11 is a good time for Pulsar to upgrade the Presto to 334+ or the
latest stable version.
On 2022/06/22 18:22:09 Enrico Olivelli wrote:
> For Pulsar 2.9 and 2.10 you should use jdk11
> you can checkout the
+1
On Mon, Jun 20, 2022 at 9:31 AM PengHui Li wrote:
> +1 (binding)
>
> Left a minor comment here about the field name
> https://github.com/apache/pulsar/issues/15370#issuecomment-1159870170
> Please check.
>
> Thanks,
> Penghui
>
> On Mon, Jun 20, 2022 at 9:21 AM Yubiao Feng
> wrote:
>
> > Hi
> If all topics share the same cache space, and we won't recycle space by topic.
> So when some topics are rebalanced to other brokers, the previous broker
> keeps its cache
> and results in cache space wasting.
> The topic shedding would be quite frequent under some cases, I am not sure
> how
I'd like to clarify the motivation for this PIP. My understanding is
that the primary motivation is to give clients a robust way to
classify a cluster as "healthy". The initial beneficiary of this
feature is the auto failover use case. I think the feature makes
sense, but before using the broker's
Right,
if there is constant activity on the cursor, the persisting frequency
is dictated by the rate limiter. If the forced flush is rate-limited
here it will not be a problem because the next ack operation (not
rate-limited) will eventually flush everything.
The problem the `flush()` is solving
For Pulsar 2.9 and 2.10 you should use jdk11
you can checkout the official docker images
for 2.11 we decided to go with jdk17
Enrico
Il giorno mer 22 giu 2022 alle ore 17:42 ZhangJian He
ha scritto:
>
> Enrico commented on 31 Mar. Now it's required jdk17 on master branch.
> `branch-2.10` is
Hi,
I did a quick reading and I couldn't understand the gist of this change:
The shadow topic doesn't really have it's own messages, or it's own ledgers
right? When it reads messages, it reads from the original topic ledgers. So
the only thing you need to do is sync the "metadata" - ledgers list?
Enrico commented on 31 Mar. Now it's required jdk17 on master branch.
`branch-2.10` is compatible with jdk8.
Thanks
ZhangJian He
tison 于2022年6月22日周三 23:37写道：
> Hi devs.
>
> During a review of PR-16163[1] I notice a comment from @Enrico Olivelli
> on PR-14953 said:
>
> > We are currently
Hi devs.
During a review of PR-16163[1] I notice a comment from @Enrico Olivelli
on PR-14953 said:
> We are currently still supporting jdk8 (on the server side)
However, on our README.md it recommends:
Pulsar Runtime Java Version Recommendation
pulsar master branch
Broker JavaVersion: 17
Yes, there may have multiple clients request the HC at the same time in the
AutoFailover case, so we should add some cache to reduce broker load.
On 2022/06/22 12:55:49 Enrico Olivelli wrote:
> Il giorno mer 22 giu 2022 alle ore 14:45 Cong Zhao
> ha scritto:
> >
> > Hi Enrico,
> >
> > > Also, I
Hi Enrico,
> IIUC nobody participated in the discussion.
The discussion is under the Github issue.
https://github.com/apache/pulsar/issues/15859
Please check.
Thanks,
Penghui
On Jun 22, 2022, 18:16 +0800, Enrico Olivelli , wrote:
> Hi,
> IIUC nobody participated in the discussion.
>
> it is
Il giorno mer 22 giu 2022 alle ore 14:45 Cong Zhao
ha scritto:
>
> Hi Enrico,
>
> > Also, I would like to understand in which usecase you can use the
> > binary endpoint and not the HTTP endpoint.
>
> We can't use the HTTP endpoint when the client did not have the admin auth to
> do a health
Hi Enrico,
> Also, I would like to understand in which usecase you can use the
> binary endpoint and not the HTTP endpoint.
We can't use the HTTP endpoint when the client did not have the admin auth to
do a health check. but we need it in some cases such as auto failover on the
client-side
I believe that this proposal is too broad.
the PIP reads about:
- adding HEALTHCHECK to the binary protocol
- add a HEALTHCHECK cache on the broker
Also, I would like to understand in which usecase you can use the
binary endpoint and not the HTTP endpoint.
Health Check is good for scripts and
Hi,
IIUC nobody participated in the discussion.
it is too early to start a VOTE
-1 (temporary)
Enrico
Il giorno mer 22 giu 2022 alle ore 05:26 PengHui Li
ha scritto:
>
> +1
>
> Penghui
>
> On Wed, Jun 22, 2022 at 11:16 AM Cong Zhao wrote:
>
> > Hi Pulsar Community,
> >
> > I would like to
LvLs9 commented on PR #251:
URL:
https://github.com/apache/pulsar-helm-chart/pull/251#issuecomment-1162902513
Dear @MarvinCai, could we merge that please
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL
LvLs9 commented on PR #251:
URL:
https://github.com/apache/pulsar-helm-chart/pull/251#issuecomment-1162902536
Dear @MarvinCai, could we merge that please
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL
24 matches
Mail list logo
