tuteng commented on PR #446:
URL: https://github.com/apache/pulsar-manager/pull/446#issuecomment-1097533095
@hsluoyz @fabian4 Can you add a document for it?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL
Similar to triggering the backlog threshold full processing method:
When the backlog hits the threshold, it is assumed that the user has set
the producer_exception policy, and the Error of
ProducerBlockedQuotaExceededError is returned to the client-side, so that
the user can perceive this
We also encountered the same problem. When the current limit is triggered,
fast failure is an ideal way to deal with it. In this way, the behavior of
the current limit itself can be notified to the client-side in time, and
the user can feel the behavior of the current limit, instead of letting the
Hi Kai:
Good ideas, For this PIP, there are the following confusions:
1. Does the current bundle-data strongly depend on zk for data consistency?
2. If the data of bundle-data is dumped to system-topic, can there be a
good guarantee for the real-time performance of bundle changes?
3. This
tuteng merged PR #446:
URL: https://github.com/apache/pulsar-manager/pull/446
--
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:
tuteng closed issue #445: feat: add support for Casdoor authentication
URL: https://github.com/apache/pulsar-manager/issues/445
--
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.
Copying the contents of the PIP to this thread:
- **Status**: Discussion
- **Author**: Bo Cong
- **Pull Request**:
- **Mailing List discussion**:
- **Release**: 2.11
# Motivation
Currently, the transaction coordinator does not limit the number of
active transactions, which may cause the
To clarify, I think this proposal is not seeking to add support for a
subscription rate limiter. That support was added in 2018 [0]. It is
instead seeking to make it possible to override the broker's configs
for dispatch rate limiting per subscription [1].
> On the client side, subscriptions have
-1
The rate limits that are currently in place are there to protect the Pulsar
service, to manage multi-tenancy on the broker. This is not meant as a
feature to manage demand side throttling.
In my opinion, this is best done as a client side feature. There is no
need to add complexity to
Hi -
Sorry for this delayed reply.
> On Apr 7, 2022, at 7:04 PM, Roc Marshal wrote:
>
> Hi, Dave.Thank you very much for your reply.A little
> confusions from me:- As you said, the option [2] may be only used as a
> specification to restrict the coding specification of PR test cases in the
So, based on this, it looks like we'd need to upgrade Pulsar to use BK
4.15.0 to get M1 compatibility?
What kind of changes will that introduce into Pulsar?
Devin G. Bost
On Fri, Apr 1, 2022 at 8:17 AM Nicolò Boschi wrote:
> Hi all,
>
> this is a follow-up discussion about the RocksDB upgrade
pipHi Pulsar community,
I open a pip to discuss Max active transaction limitation for
transaction coordinator.
link: https://github.com/apache/pulsar/issues/15133
Thanks,
Bo
LoveEachDay commented on PR #258:
URL:
https://github.com/apache/pulsar-helm-chart/pull/258#issuecomment-1096573551
/cc @tuteng
--
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
tuteng opened a new pull request, #456:
URL: https://github.com/apache/pulsar-manager/pull/456
Remove github social login
Disable cluster page
*(If this PR fixes a github issue, please add `Fixes #`.)*
Fixes #
*(or if this PR is one task of a github issue, please
LoveEachDay opened a new pull request, #258:
URL: https://github.com/apache/pulsar-helm-chart/pull/258
Signed-off-by: Edward Zeng
Fixes #257
### Motivation
Fix PodMonitor name conflicts for multiple releases in same namespace
### Modifications
Use release
LoveEachDay commented on issue #257:
URL:
https://github.com/apache/pulsar-helm-chart/issues/257#issuecomment-1096560953
/assign @LoveEachDay
--
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
LoveEachDay opened a new issue, #257:
URL: https://github.com/apache/pulsar-helm-chart/issues/257
**Describe the bug**
Install two releases of pulsar cluster with podMonitor enabled in the same
namespace will fail.
**To Reproduce**
Steps to reproduce the behavior:
1.
tuteng merged PR #444:
URL: https://github.com/apache/pulsar-manager/pull/444
--
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:
tuteng closed issue #443: Simplify the classpath in the bin/pulsar-manager
script
URL: https://github.com/apache/pulsar-manager/issues/443
--
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
tuteng merged PR #448:
URL: https://github.com/apache/pulsar-manager/pull/448
--
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:
20 matches
Mail list logo
