2019-05-31 13:31:52 UTC - Ben Poole: Is it possible to access the number of consumers that are subscribed (or currently connected) to a particular topic through the Java api client? ---- 2019-05-31 15:20:38 UTC - Chris Bartholomew: You can get this type of information from the REST API from the topic stats. It looks to be supported in the Java API client too. <https://pulsar.apache.org/docs/en/admin-api-persistent-topics/#get-stats> ---- 2019-05-31 15:24:28 UTC - Ben Poole: Ah thanks, I missed this! ---- 2019-05-31 15:47:33 UTC - Matteo Merli: It’s supported in the Java admin client: <https://pulsar.apache.org/api/admin/org/apache/pulsar/client/admin/Topics.html#getStats-java.lang.String-> ---- 2019-05-31 16:40:19 UTC - Sam Leung: I have a question about client-side metrics. I see there is ProducerStats/ConsumerStats, and Interceptors. It looks like stats was built only to be printed out to console, as it accumulates, then on a timer, grabs the latest value and resets the accumulator, then prints out the value without saving the “last” values. Is there some way for me to send the per (minute by default) stats to my metrics collector? If I just call something like `producer.getStats().getNumMsgsSent()`, I only get the instantaneous value within the 60s window which is not useful. ---- 2019-05-31 16:41:47 UTC - Matteo Merli: You can either use `getTotalMsgsSent()` or `getSendMsgsRate()` ---- 2019-05-31 16:47:49 UTC - Sam Leung: Makes sense, we’ll see if we can make do with the totals and rates. Thanks. ---- 2019-05-31 16:49:01 UTC - Matteo Merli: Are you trying to expose through Prometheus? ---- 2019-05-31 16:51:08 UTC - Sam Leung: Our current toolchain is to send to statsd ---- 2019-05-31 18:58:59 UTC - Sam Leung: Rate and latency are not accumulated for partitioned topics in `ProducerStatsRecorderImpl.updateCumulativeStats`, is this intentional? ---- 2019-05-31 19:07:09 UTC - Matteo Merli: No, I think that’s wrong :confused: ---- 2019-05-31 19:37:16 UTC - Addison Higham: hrm... I am trying to look at the storage offloader code and it seems like the shading of jcloud is not playing well with intellij ---- 2019-05-31 19:38:26 UTC - Addison Higham: anyone else ever experience that? ---- 2019-05-31 19:57:10 UTC - Ashley Pallarito: @Ashley Pallarito has joined the channel ---- 2019-05-31 19:58:10 UTC - Thor Sigurjonsson: Hi Ashley! wave : Ashley Pallarito, Karthik Ramasamy ---- 2019-05-31 20:41:42 UTC - Sijie Guo: are you pull in the latest master? If so, the shaded jcloud should be pinned a specific version. hence intellij should be able to handle it properly. ---- 2019-05-31 20:45:49 UTC - Addison Higham: It was still doing it on latest master, I was able to work around it by ignoring the jcloud-shaded subproject, or at least, it isn't yelling at me now, not sure if running tests would work ---- 2019-05-31 20:46:03 UTC - Addison Higham: though it isn't resolving source jars ---- 2019-05-31 20:49:18 UTC - Sijie Guo: if you are looking for jcloud source jar, it won’t work out since it is already shaded. If you figured out how to resolve it, please contribute it back :slightly_smiling_face: ---- 2019-05-31 21:14:37 UTC - danielskidmore: @danielskidmore has joined the channel ---- 2019-05-31 21:22:20 UTC - Sam Leung: Okay I’ll file a bug ---- 2019-05-31 21:23:03 UTC - Matteo Merli: :+1: ---- 2019-05-31 22:15:37 UTC - Addison Higham: quick question: is the reference configuration file generated? or do any new configuration options need to be added to it manually? ---- 2019-05-31 22:18:09 UTC - Matteo Merli: At this point is not auto-generated. We did the first part though, the `ServiceConfiguration` class has annotations with the docs for each field. We just need a CLI tool to read these annotations and re-generate the `broker.conf` file (and the markdown files for the website). ---- 2019-05-31 22:18:33 UTC - Addison Higham: okay cool, no worries ---- 2019-05-31 22:27:05 UTC - Addison Higham: I was just starting in on configuring s3 offloading and got annoyed with not being able to use ec2 instance credentials, so I fixed it: <https://github.com/apache/pulsar/pull/4433> +1 : Matteo Merli, David Kjerrumgaard clap : David Kjerrumgaard, Joe Francis, Shivji Kumar Jha ---- 2019-05-31 22:38:36 UTC - Addison Higham: oh also, IDK how you would integration test that unless you are using a real ec2 instance, but I figured that so long as the existing integration tests pass and there are some sane unit tests, that may be sufficient :shrug: ---- 2019-05-31 22:48:36 UTC - Addison Higham: I am going to backport that into 2.3 and test it on our dev clusters +1 : David Kjerrumgaard, Shivji Kumar Jha ---- 2019-06-01 00:00:45 UTC - Grant Wu: <http://pulsar.apache.org/en/admin-rest-api/> are these docs versioned? ---- 2019-06-01 00:01:18 UTC - Grant Wu: <http://pulsar.apache.org/docs/en/2.1.0-incubating/admin-api-overview/#rest-api> seems to link to the unversioned version of this ---- 2019-06-01 00:02:30 UTC - Matteo Merli: Not at this point. That’s why I started <https://github.com/apache/pulsar/pull/4420> ---- 2019-06-01 00:03:42 UTC - Jerry Peng: @Jerry Peng set the channel topic: Pulsar graduated as a Top-Level project :tada: - Pulsar release 2.3.2 - <http://pulsar.apache.org/release-notes/#2.3.2> beers : Matteo Merli, Penghui Li, Yong Zhang, Yuvaraj Loganathan tada : Penghui Li, Yong Zhang, lan ---- 2019-06-01 00:04:27 UTC - Jerry Peng: <!here> Apache Pulsar 2.3.2 is officially release!
<http://pulsar.apache.org/release-notes/#2.3.2> clap : Thor Sigurjonsson, Penghui Li, Chris Bartholomew, Ali Ahmed, Karthik Ramasamy, tuteng, jia zhai, Yuvaraj Loganathan tada : David Kjerrumgaard, Ali Ahmed, Karthik Ramasamy, jia zhai, lan, Shivji Kumar Jha beers : jia zhai ---- 2019-06-01 00:09:58 UTC - Grant Wu: is there any way I can get to the old version of these docs on an ad-hoc basis? ---- 2019-06-01 00:13:18 UTC - Matteo Merli: Other that check out the old tag and regenerate, I don’t think there are many other options ---- 2019-06-01 00:13:26 UTC - Grant Wu: :confused: ----
