+1(non-binding)
Anon Hxy 于2022年8月16日周二 13:11写道：
> Dear Community,
>
> I'd like to start a VOTE on "PIP-191: Support batched message using entry
> filter."
>
> The proposal can be read at [0] and the discussion thread is available at
> [1]
>
> Voting will stay open for at least 48h.
>
> [0] https
gurleen-gks commented on issue #310:
URL: https://github.com/apache/pulsar-manager/issues/310#issuecomment-1216188380
However now I am struggling with the below error
```
at
io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:499)
~[netty-transport-4.1.24.
I agree that metrics on these "blocked" producers are helpful to end users.
> Another concern is that if the topic is unloaded to another broker, we have
> to notify the client to reconnect, I'm not sure if
> `waitingExclusiveProducers` does that or if I missing some logic.
If I remember correc
gurleen-gks commented on issue #310:
URL: https://github.com/apache/pulsar-manager/issues/310#issuecomment-1216186997
Yes, it is fixed
--
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
Good idea, it makes sense to me to add this to the proxy.
> BTW, are there any side effects from the implementation?
Reading through the code from
https://github.com/apache/pulsar/pull/10754, it looks like the cost is
minimal. The broker maintains counters for each IP address, and they
are increm
Dear Community,
I'd like to start a VOTE on "PIP-191: Support batched message using entry
filter."
The proposal can be read at [0] and the discussion thread is available at
[1]
Voting will stay open for at least 48h.
[0] https://github.com/apache/pulsar/issues/16680
[1] https://lists.apache.org
Sounds good. It's good for server stability.
BTW, are there any side effects from the implementation?
On Tue, Aug 16, 2022 at 10:33 AM mattison chao
wrote:
> Hi, All
>
> Pulsar has the `brokerMaxConnectionsPerIp` configuration at the
> broker, we can use it to limit the maximum connections per
Hi Dave,
> Just remove that command. Having two servers should be enough.
Agree, I have removed it.
> Release candidates should not be made by a bot. Releases must be verified
by building them from source. See
https://www.apache.org/legal/release-policy.html#owned-controlled-hardware
Thanks for
Hi Xiangying
>> Can the sequence id generation strategy be added to the proposal？
> think it's an implementation detail that shouldn't be exposed to the user
at all.
OK.
Thanks
Yubiao Feng
On Mon, Aug 15, 2022 at 8:11 PM Xiangying Meng wrote:
> Hi, yubiao,
> I think it's an implementation d
urfreespace merged PR #166:
URL: https://github.com/apache/pulsar-site/pull/166
--
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.a
Bumping up this thread.
-Lari
pe 20. toukok. 2022 klo 1.57 Lari Hotari kirjoitti:
> Hi all,
>
> I started writing this email as feedback to "PIP-157: Bucketing topic
> metadata to allow more topics per namespace" [3].
> This email expanded to cover some analysis of "PIP-45: Pluggable metadata
>
Hi, All
Pulsar has the `brokerMaxConnectionsPerIp` configuration at the
broker, we can use it to limit the maximum connections per IP.
The original motivation and PR here: https://github.com/apache/pulsar/pull/10754
IMO, we can also apply it to pulsar-proxy, because when a large
number of proxy
urfreespace merged PR #165:
URL: https://github.com/apache/pulsar-site/pull/165
--
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.a
rdhabalia merged PR #482:
URL: https://github.com/apache/pulsar-manager/pull/482
--
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.
tisonkun commented on PR #56:
URL: https://github.com/apache/pulsar-test-infra/pull/56#issuecomment-1215319343
ping @maxsxu @michaeljmarshall
--
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
> On Aug 15, 2022, at 3:30 AM, Haiting Jiang wrote:
>
>> Maybe we'd better move the release process doc and validation doc
>> to the codebase, not the wiki pages.
>
> IMO, we can move all contributor documentation and committers documentation
> to codebase.
> One example is that `pool.sks-key
> On Aug 15, 2022, at 4:09 AM, Yunze Xu wrote:
>
>> One example is that `pool.sks-keyservers.net` in [1] seems not available
> anymore, but I am not that confident enough to edit it directly.
>
> Yeah. It’s not available in my env as well. I made some changes recently,
> but I’m also not sure
Hi, yubiao,
I think it's an implementation detail that shouldn't be exposed to the user
at all.
Yours sincerely,
Xiangying Meng
On Mon, Aug 15, 2022 at 8:02 PM Yubiao Feng
wrote:
> Hi Xiangying
>
> Thank you for your reply. Sorry, I have one more question:
>
> > If these operations are failed at
Hi Xiangying
Thank you for your reply. Sorry, I have one more question:
> If these operations are failed at operation 2, the old snapshots will be
covered by the new large snapshot when compact due to they have the same
sequence ID.
Can the sequence id generation strategy be added to the doc？
O
> One example is that `pool.sks-keyservers.net` in [1] seems not available
anymore, but I am not that confident enough to edit it directly.
Yeah. It’s not available in my env as well. I made some changes recently,
but I’m also not sure about this point.
> I think we can consider using a BOT (like
Hi, yubiao,
First of all, thanks for the attention and questions. Then for your three
questions:
1.
> Does the merge take place in memory or in BK?
The snapshot will merge in BK. For specific details, you can see detailed
instructions in the* ### Merge snapshot section.*
2.
>How do we ensure the a
Hi team,
Feel free to choose your desired convention **before EOD 8/16 (UTC +8)**.
We'll close this discussion and move to the next topic after that time.
Thank you!
Yu and mangoGoForward
On Mon, Aug 15, 2022 at 6:27 PM Yu wrote:
> Hi tison,
>
> Thanks for your suggestions!
>
> > But followi
> Maybe we'd better move the release process doc and validation doc
> to the codebase, not the wiki pages.
IMO, we can move all contributor documentation and committers documentation
to codebase.
One example is that `pool.sks-keyservers.net` in [1] seems not available
anymore, but I am not that co
SignorMercurio opened a new pull request, #164:
URL: https://github.com/apache/pulsar-site/pull/164
Remove exec command in pulsar-config-doc-gen.sh so that the docs can be
successfully generated. @urfreespace
--
This is an automated message from the Apache Git Service.
To respond to the
Hi tison,
Thanks for your suggestions!
> But following the Conventional Commits will ensure we can use the
toolchain
built around it, such as semantic release[1].
Our customized convention can use the semantic release tool as well.
> Also, Conventional Commits
have a standard to name a BREAKING
urfreespace merged PR #163:
URL: https://github.com/apache/pulsar-site/pull/163
--
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.a
SignorMercurio opened a new pull request, #163:
URL: https://github.com/apache/pulsar-site/pull/163
Fix non-existing directory in pulsar-config-doc-gen.sh. @urfreespace
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use
momo-jun commented on issue #146:
URL: https://github.com/apache/pulsar-site/issues/146#issuecomment-1214767571
> For the feature matrix, it's mainly tracking feature points and whether it
has a document entry. Once we add document to all those features, we may simply
remove that matrix.
urfreespace merged PR #162:
URL: https://github.com/apache/pulsar-site/pull/162
--
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.a
SignorMercurio opened a new pull request, #162:
URL: https://github.com/apache/pulsar-site/pull/162
Fix wrong path in pulsar-config-doc-gen.sh. @urfreespace
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL abov
Hi Xiangying
I think Multiple-snapshots for TB is a good idea. And I have these
questions:
> The number of the transactions in a snapshot can be configured, and we
hope it is small, then we can merge the small snapshots into a large
snapshot when it reaches a configured number.
Does the merge t
31 matches
Mail list logo
