[GitHub] [pulsar-client-node] iamrmin commented on issue #141: Event listener if client disconnect or connection interruption

iamrmin commented on issue #141: URL: https://github.com/apache/pulsar-client-node/issues/141#issuecomment-786419050 @massakam I see. Thank you :) This is an automated message from the Apache Git Service. To respond to the m

[GitHub] [pulsar-client-node] massakam edited a comment on issue #141: Event listener if client disconnect or connection interruption

massakam edited a comment on issue #141: URL: https://github.com/apache/pulsar-client-node/issues/141#issuecomment-786417959 @iamrmin On the producer side, we should be able to notice that the connection has been lost because message sending times out (the duration can be changed with the

[GitHub] [pulsar-client-node] massakam commented on issue #141: Event listener if client disconnect or connection interruption

massakam commented on issue #141: URL: https://github.com/apache/pulsar-client-node/issues/141#issuecomment-786417959 @iamrmin On the producer side, we can notice that the connection has been lost because message sending times out (the duration can be changed with the `sendTimeoutMs` prop

Re: [DISCUSS] Log Levels for Broker's ServerCnx Class

I'd like to approach this from a different angle. At a very high level we can expect to see two types of users: 1. Early adopters generally want to understand Pulsar's design, how the pieces fit together, and why 2. Mainstream users just want it to work, preferably with as little attention from

[jira] [Updated] (PULSAR-9) Improve the message written count metrics for the topic

[ https://issues.apache.org/jira/browse/PULSAR-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Penghui Li updated PULSAR-9: Description: Currently, Pulsar exposes the message written count metrics though the Prometheus endpoint, and

[jira] [Reopened] (PULSAR-9) Improve the message written count metrics for the topic

[ https://issues.apache.org/jira/browse/PULSAR-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Penghui Li reopened PULSAR-9: - > Improve the message written count metrics for the topic > ---

Re: Pulsar Server on JDK11 - initial discussion

Just an update. I have started to tests failures on CI regarding JDK11 I am using my github fork in order not to pollute the shared CI If you are curious you can see the results in this branch https://github.com/eolivelli/pulsar/pull/6 I will create issues for every finding, like this https://gi

First Flink x Pulsar Bay Area Virtual Meetup - All things about Streaming SQL

Hi all, We are thrilled to announce the first-ever Flink x Pulsar meetup on March 16th & 17th! This meetup is all things about streaming SQL! It is a two-day virtual event co-hosted by Uber, Ververica, and StreamNative! You will learn about how Uber and Facebook build and optimize their streaming

Re: [E] Re: [PIP-78] Split the individual acknowledgments into multiple entries

Matteo, Rajan, Joe, Addison, Penghui, and Jia have met today to discuss this issue. We have come up with next steps: In general, we have agreed to proceed with the PIP. 1. Penghui is going to update the PIP to clarify terminology and diagrams in the PIP. He will also write more details about how

Re: [DISCUSS] Log Levels for Broker's ServerCnx Class

I don't think we should change the log level by default. Certain log information has been very valuable for real production issues. They exist there from many years' experience. Instead of changing the log level in the code, a better way is to add a logger in log4j2.xml to change the log level for