You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@pulsar.apache.org by Apache Pulsar Slack <ap...@gmail.com> on 2019/07/25 09:11:03 UTC
Slack digest for #general - 2019-07-25
2019-07-24 09:16:05 UTC - Lewey: Hi, I am trying to limit the consumer rate on a topic how ever the command found in the documentation is not working, `pulsar-admin namespaces set-subscription-dispatch-rate my-tenant/my-namespace -md 350000`
----
2019-07-24 10:00:56 UTC - Venugopal Doddi: @jia zhai I am going thru this link (<https://github.com/apache/pulsar/wiki/PIP-26:-Delayed-Message-Delivery>) and saying status as`Status: Proposed` , meaning this is a feature that is requested to add? or is already in place? I am not seeing any reference regarding this in pulsar docs. can you please share your thoughts on this? @Sijie Guo
----
2019-07-24 10:49:49 UTC - Sijie Guo: @Venugopal Doddi sorry we forgot to update the status. the feature is already in 2.4.0. Let me double check if the pulsar docs is updated. If not, I will create issues to address it.
for your convenience,
1) you can check the 2.4.0 blog: <https://pulsar.apache.org/blog/2019/07/05/Apache-Pulsar-2-4-0/> for an example.
2) you can check section “Example of delayed message delivery” in this blog post (<https://medium.com/streamnative/whats-new-in-apache-pulsar-2-4-0-d646f6727642>). There are two examples about delayed delivery.
----
2019-07-24 10:50:35 UTC - Sijie Guo: Can you describe more about the errors you are seeing when running this command?
----
2019-07-24 10:57:56 UTC - Alexandre DUVAL: @Yuvaraj Loganathan it divided disk usage by 2.
----
2019-07-24 10:58:12 UTC - Alexandre DUVAL: from 16GB used on each node to 7GB.
----
2019-07-24 10:59:02 UTC - Yuvaraj Loganathan: Cool :thumbsup:
----
2019-07-24 11:21:51 UTC - Venugopal Doddi: @Sijie Guo thanks alot..
----
2019-07-24 11:21:57 UTC - Venugopal Doddi: this helps
----
2019-07-24 12:14:25 UTC - Lewey: this `set-subscription-dispatch-rate` function doesnt seem to exist, im guessing this is because we are using version 2.1.0?
----
2019-07-24 12:38:01 UTC - Sijie Guo: @Lewey if you are using 2.1.0, please checkout the 2.1.0 documentation then. <https://pulsar.apache.org/docs/en/2.1.0-incubating/admin-api-namespaces/>
----
2019-07-24 15:27:17 UTC - Don Albrecht: @Don Albrecht has joined the channel
----
2019-07-24 15:31:28 UTC - Ryan Samo: Hey guys,
I’m looking at the logTopic capabilities for Pulsar functions and I see that under the covers it uses a LogEvent from sfl4j. When you use the logger and it outputs to the logTopic, it writes out as a byte[]. My question is on the consumption side of the logTopic, how are you guys deserializing the byte[] to LogEvent objects without telling Pulsar that the logTopic schema should be of type LogEvent?
Just trying to figure out how to consume log events that are only of type ERROR for example.
----
2019-07-24 15:36:15 UTC - Grant Wu: <http://pulsar.apache.org/en/admin-rest-api/#operation/resetCursorOnPosition> how do I specify the message ID for this endpoint?
----
2019-07-25 02:38:03 UTC - 3180299040: @3180299040 has joined the channel
----
2019-07-25 05:14:33 UTC - divyasree: @Sijie Guo Can you explain me the global configuration store concept?
----
2019-07-25 05:28:39 UTC - Venugopal Doddi: @Sijie Guo We are currently on 2.3.0 version and as you say the delayed-message-delivery is in 2.4.0. When i look for the documentation how can i upgrde? and i dont see any. What is the recommended way to do this?
----
2019-07-25 05:35:08 UTC - Sijie Guo: I added an ugprade guide a few days ago. I think it should be alive in the latest version of documentation. I attached the markdown file below for your convenience .
<https://github.com/apache/pulsar/blob/master/site2/docs/administration-upgrade.md>
----