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 2018/12/03 09:11:03 UTC
Slack digest for #general - 2018-12-03
2018-12-02 09:39:24 UTC - Pavel Vetokhin: Single node cluster setup works <https://kubernetes.io/docs/setup/independent/create-cluster-kubeadm/>
----
2018-12-02 09:42:53 UTC - Pavel Vetokhin: What is the best way to deploy function jar to the Pulsar broker (Kubenetes)?
----
2018-12-02 09:47:34 UTC - Sijie Guo: Currently functions can be run in three mode, process, thread and k8s. For the first 2, they run on functions worker machines, if you deploy function worker as part of brokers, then they will be running on broker machines. If you already run pulsar on k8s, you can configure broker to enable k8s runtime, so functions will be run as individual pods in k8s
----
2018-12-02 11:12:22 UTC - Pavel Vetokhin: Currently i want to run functions in the thread mode on the k8s broker. What is the right way to deploy jars to it? Do i need copy jar into the volume of the pulsar admin pod or install pulsar admin util locally?
----
2018-12-02 11:14:17 UTC - Pavel Vetokhin: Are there another possible ways to deploy jars?
----
2018-12-02 15:22:01 UTC - Matteo Merli: @Pavel Vetokhin in any deployment mode, when you “submit” a function, its code (jar, py file or zip) gets uploaded and stored in Bookkeeper. There’s no need to copy jars or to place jars somewhere
----
2018-12-02 16:27:08 UTC - Yifan: Hi, I would like to read all messages in topic until now. I am thinking that I have to read current message, save it, then seek to latest, save the latest message, seek back to saved current message, read until I reach the save latest message. But this will not work if there is no latest message. Is there better way to do this?
----
2018-12-02 16:44:48 UTC - Matteo Merli: @Yifan You can create a `Reader` that starts on `MessageId.earliest` and then check the publish timestamp of the messages, stopping when ts > now
----
2018-12-02 16:46:21 UTC - Yifan: Of course, I forgot the messages timestamps :stuck_out_tongue:
----
2018-12-02 16:46:25 UTC - Yifan: thanks
----
2018-12-02 16:52:58 UTC - Pavel Vetokhin: @Matteo Merli, i can "submit" only with pulsar admin utulity? There is no other ways?
----
2018-12-02 16:57:18 UTC - Matteo Merli: Or through REST API (or java Admin API)
----
2018-12-02 17:11:22 UTC - Pavel Vetokhin: I see it. Thanks a lot!
Are that documented somewhere?
----
2018-12-02 19:08:11 UTC - David Kjerrumgaard: @Pavel Vetokhin The information you are looking for is a bit spread out, but the Java Admin API can be found here: <https://pulsar.apache.org/docs/en/admin-api-overview/> and the REST API is here <http://pulsar.apache.org/en/admin-rest-api/#/>
+1 : Pavel Vetokhin
----
2018-12-02 20:47:14 UTC - eolivelli: Is the message timestamp guaranteed to increase monotonically?
----
2018-12-03 02:44:31 UTC - Matteo Merli: @eolivelli not exactly. Timestamps are set by client library (as in currentTimeMillis()). Clock skews or network delays between different producers can lead to interleaved timestamps.
We thought at some point to introduce monotonic timestamps in broker, though never got the time to actually implement it, though it shouldn’t too hard to do.
In general, for most cases, the current approach should work fine, but yes it’s not exactly precise
----
2018-12-03 06:14:05 UTC - eolivelli: That what my guess. Thank you for your explanation
----