Audace commented on issue #1875: Problems with Persistent Topic stats URL: https://github.com/apache/incubator-pulsar/issues/1875#issuecomment-393619284 Ah that’s helpful. So in that case if the consumer receives 1000 messages in a batch, it will be 0.0 until all 1000 are processed and more messages are fetched? Is there a stat that tracks ack more closely? On Thu, May 31, 2018 at 1:43 PM Matteo Merli <[email protected]> wrote: > @Audace <https://github.com/Audace> I cannot see this problem here. Stats > are looking correct to me. Just try to do a simple test: from 3 different > consoles, run: > > pulsar-perf produce my-topic > > pulsar-perf consume my-topic > > pulsar-admin topics stats my-topic > > The default rate is 100msg/s and it's showing up correctly even after a > while. > > Perhaphs, can you just add the json stats here? > > msgRateOut to reflect the number of messages published and number of > messages ack'd, respectively. > > msgRateOut is the rate at which the broker pushes messages to a consumer, > in some case it might be different from the rate that consumer > "acknowledges" the messages, since the flow-control is based on application > calling consumer.receive() rather than on the ack itself. > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <https://github.com/apache/incubator-pulsar/issues/1875#issuecomment-393615109>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/ADuJLzoF983JrGwT-k55djvkfZyyvfQHks5t4CumgaJpZM4UVJqX> > . >
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
