[GitHub] [pulsar-helm-chart] chrisjohnson00 commented on issue #65: Helm chart dependencies do not follow best practices

chrisjohnson00 commented on issue #65: URL: https://github.com/apache/pulsar-helm-chart/issues/65#issuecomment-894615515 +1 This would also fix the improper use of Prometheus as a deployment. Prometheus needs to be a stateful set due to it's pvc. -- This is an automated message from

Re: Lack of retries on TooManyRequests

Suppose you have about a million topics and your Pulsar cluster goes down (say, ZK down). ..many millions of producers and consumers are now anxiously awaiting the cluster to comeback. .. fun experience for the first broker that comes up. Don't ask me how I know, ref blame ServerCnx.java#L429

Re: PIP-89: Structured documented logging for Pulsar

Responses inline as well On Fri, Aug 6, 2021 at 9:16 AM Ivan Kelly wrote: > >For example, in the proposed scenario it's used "Events.LOOKUP". > > There is a lot of context that would be missing there. Eg: is this an > > HTTP or Protobuf lookup, did we log when the operation started or when >

[GitHub] [pulsar-client-node] Liapin opened a new pull request #168: Branch 1.3

Liapin opened a new pull request #168: URL: https://github.com/apache/pulsar-client-node/pull/168 Fixes Use Buffer::Copy instead of Buffer::New #163 Fix leak at MessageId::Serialize #160 Fix Leak in MessageId::ToString #159 -- This is an automated message from the Apache Git Serv

Re: Lack of retries on TooManyRequests

Inline > In that scenario, > should we block or fail fast and let the application decide which is what > we do today? Also, should we distinguish between the two scenarios, i.e. > broker sends the error vs client internally throws the error? While I agree that the client limit is different to the

Re: Lack of retries on TooManyRequests

Currently, there are two ways to get the TooManyRequest errors in the client. 1) The client enforces a maximum number of pending lookups: https://github.com/apache/pulsar/blob/master/pulsar-client/src/main/java/org/apache/pulsar/client/impl/ClientCnx.java#L733 The max number can be set when cre

Re: Lack of retries on TooManyRequests

Another strangeness I've seen with partition metadata requests. https://github.com/apache/pulsar/blob/ddb5fb0e062c2fe0967efce2a443a31f9cd12c07/pulsar-client/src/main/java/org/apache/pulsar/client/impl/PulsarClientImpl.java#L886 It takes a backoff, and it does retries, but the opTimeoutMs variable

[GitHub] [pulsar-dotpulsar] blankensteiner closed issue #82: How to create a new topic by dotpulsar?

blankensteiner closed issue #82: URL: https://github.com/apache/pulsar-dotpulsar/issues/82 -- 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-uns

[GitHub] [pulsar-dotpulsar] blankensteiner commented on issue #84: Recover after network disconnect

blankensteiner commented on issue #84: URL: https://github.com/apache/pulsar-dotpulsar/issues/84#issuecomment-894401433 Hi @Flipbed Are you [monitoring](https://github.com/apache/pulsar-dotpulsar/wiki/Monitoring) the state? You can also have a look at the [sample](https://github.co

Re: PIP-89: Structured documented logging for Pulsar

Thanks for the detailed feedback Matteo, Responses inline. > 1. I like the idea of using enum to identify an event, but I fear > that the enum name itself will not be, in many cases, as expressive of > the context as a complete phrase. I'm not convinced by this. From just eyeballing one of our

[GitHub] [pulsar-dotpulsar] Flipbed opened a new issue #84: Recover after network disconnect

Flipbed opened a new issue #84: URL: https://github.com/apache/pulsar-dotpulsar/issues/84 Hi Everyone! We have just started using DotPuslar and mostly it works great! We are having an issue where we _think_ that our company network goes offline for a while, and when coming bac

[Pulsar Community Weekly Update] 2021-07-26 ~ 2021-08-01

Hi Pulsar Community, The latest Pulsar Weekly update is here! Welcome to check the Pulsar community weekly update for 07/26, 2021 - 08/01, 2021. First, we would like to thank the contributors of the following Github ID who helped build Pulsar during the week: frankxieke, massakam, Sunny-Island,

[Pulsar Community Weekly Update] 2021-07-26 ~ 2021-08-01

Hi Pulsar Community, The latest Pulsar Weekly update is here! Welcome to check the Pulsar community weekly update for 07/26, 2021 - 08/01, 2021. First, we would like to thank the contributors of the following Github ID who helped build Pulsar during the week: > frankxieke, massakam, Sunny-Islan