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/10/15 09:11:03 UTC
Slack digest for #general - 2019-10-15
2019-10-14 10:00:11 UTC - Vladimir Shchur: Hi! Trying to test compaction, I've run `bin/pulsar-admin topics compact <persistent://public/retention/topic-2>` command and got 500 error `"PUT /admin/v2/persistent/public/retention/topic-2/compaction?authoritative=true HTTP/1.1" 500 6576 "-" "Pulsar-Java-v2.4.1" 7`, then tried to run query through REST api manually and got this response:
```
org.apache.pulsar.broker.PulsarServerException: org.apache.pulsar.broker.PulsarServerException: java.lang.IllegalArgumentException: Param serviceUrl must not be blank.
at org.apache.pulsar.broker.PulsarService.getCompactor(PulsarService.java:809)
at org.apache.pulsar.broker.service.persistent.PersistentTopic.triggerCompaction(PersistentTopic.java:1775)
at org.apache.pulsar.broker.admin.impl.PersistentTopicsBase.internalTriggerCompaction(PersistentTopicsBase.java:1262)
at org.apache.pulsar.broker.admin.v2.PersistentTopics.compact(PersistentTopics.java:838)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
...
```
full stacktrace here <https://pastebin.com/iUAS07LB>
UPD: tried to run it through `bin/pulsar` and got bunch of other errors <https://pastebin.com/ft8THHnC>
----
2019-10-14 10:02:46 UTC - snowcrumble: @snowcrumble has joined the channel
----
2019-10-14 11:59:56 UTC - Viswa Six: @Viswa Six has joined the channel
----
2019-10-14 12:04:20 UTC - Eno Thereska: @Eno Thereska has joined the channel
----
2019-10-14 15:08:01 UTC - David Kjerrumgaard: @Vladimir Shchur The documentation for the `pulsar-admin` tool isn't great. It neglects to show the common switches that are available. You will need to specify the `--admin-url`
----
2019-10-14 16:15:11 UTC - Joe Olson: @Joe Olson has joined the channel
----
2019-10-14 16:43:31 UTC - Vladimir Shchur: @David Kjerrumgaard Thanks for suggestion, but it makes no difference. As I said, I made REST direct calls where I was able to see the actual 500 error response.
----
2019-10-14 16:44:52 UTC - Vladimir Shchur: pulsar-admin command just returns 500 error with `admin-url` parameter and without it
----
2019-10-14 18:55:04 UTC - Tim Howard: I have the changes necessary to add DeliverAt to the go client, is it acceptable to make a PR on your branch in your fork?
----
2019-10-14 18:55:16 UTC - Tim Howard: The branch for the C++/C client code?
----
2019-10-14 19:00:58 UTC - Matteo Merli: Just do rolling upgrades of each process — There are no incompatibilities.. You can also rollback to 2.3 if you encounter any issue with a new version.
----
2019-10-14 19:26:15 UTC - Addison Higham: @Vladimir Shchur what do you have set for `brokerServicePort` in your broker.conf
----
2019-10-14 19:28:41 UTC - lechidungvl: @lechidungvl has joined the channel
----
2019-10-14 19:28:42 UTC - Satish Gadey: @Satish Gadey has joined the channel
----
2019-10-14 19:28:42 UTC - kangsiqi: @kangsiqi has joined the channel
----
2019-10-14 19:28:43 UTC - Jaime Cernuda95: @Jaime Cernuda95 has joined the channel
----
2019-10-14 19:28:43 UTC - jcernudagarcia: @jcernudagarcia has joined the channel
----
2019-10-14 19:28:43 UTC - 1030586475: @1030586475 has joined the channel
----
2019-10-14 19:28:45 UTC - Addison Higham: bit of background: For some http calls, pulsar makes an HTTP call back to itself. It discovers the hostname by either looking at `advertisedAddress` or just figuring out the IP of your listening interface. However, If you don't have the `port` property set to be empty, it doesn't know what port to call itself back on so it fails to resolve a serviceUri
----
2019-10-14 19:30:48 UTC - Vladimir Shchur: # Port to use to server HTTP request
webServicePort=8080
This is what I have in config of bastion pod which issues http request
----
2019-10-14 19:32:02 UTC - Addison Higham: this is for your broker config
----
2019-10-14 19:33:18 UTC - Vladimir Shchur: Yes, inside broker.config on broker side (as well as on bastion side) I have
# Broker data port
brokerServicePort=6650
----
2019-10-14 19:46:10 UTC - Alex: @Alex has joined the channel
----
2019-10-14 19:46:39 UTC - Vladimir Shchur: Opened issue <https://github.com/apache/pulsar/issues/5384>
----
2019-10-14 19:49:18 UTC - Alex: How do I build fanout-like messaging using pulsar?
For example, I want to build scalable websocket service - but is there a way to know what consumer (in a failover mode) currently consumes messages (so I can redirect WS clients to this node)?
----
2019-10-14 20:13:11 UTC - Jacek Machura: @Jacek Machura has joined the channel
----
2019-10-14 20:36:02 UTC - Matteo Merli: You can pass a `ConsumerEventListener` when subscribing to the topic.
<https://pulsar.apache.org/api/client/org/apache/pulsar/client/api/ConsumerEventListener.html>
----
2019-10-14 20:36:22 UTC - Matteo Merli: It will notify when the failover consumer is the actual active consumer
----
2019-10-14 20:38:08 UTC - Alex: @Matteo Merli thanks, that's what I'm looking for! Is it intended to be used in a failover mode only?
----
2019-10-14 20:38:18 UTC - Matteo Merli: Yes
----
2019-10-14 20:38:43 UTC - Matteo Merli: for the other modes, the active status is not relevant, since the consumer will always be active
----
2019-10-14 20:40:11 UTC - Alex: Cool, will try it!
----
2019-10-14 20:57:25 UTC - Sijie Guo: Currently XA is not planned as part of transaction. However since the design is a two-phase commit, I don’t see a problem to support XA transactions in the future. Once we complete the transaction implementation, we can look into XA support.
> I also wanted to understand why would we not support serializability.
Currently the transaction is more or less atomic writes. There is no mutations in the transaction. So we didn’t take serializability into account. However if we are going to support XA, we have to consider serializability.
----
2019-10-14 20:58:10 UTC - Sijie Guo: I think it was set to 10 seconds to avoid any misconfiguration. Because less than 10 seconds you are easily to be volatile to jvm pauses.
----
2019-10-14 21:19:47 UTC - Shishir Pandey: Got it! Thank you.
----
2019-10-14 22:44:14 UTC - Luke Lu: Hey guys, how does auth work with websocket client? Would adding the Authorization: Bearer <token> header work if token auth is enabled on broker? It’s not clear on the doc but the source seems to indicate that it might work.
----
2019-10-14 22:48:22 UTC - Ali Ahmed: this might be useful for pulsar k8 installations
<https://github.com/pravega/zookeeper-operator>
----
2019-10-14 22:51:20 UTC - Luke Lu: This only works with zk 3.5+. Doesn’t pulsar currently rely on 3.4.x?
----
2019-10-14 22:54:17 UTC - Ali Ahmed: we need to get the pr merged
<https://github.com/apache/pulsar/pull/5043/files>
----
2019-10-15 00:19:53 UTC - Sijie Guo: Pulsar doesn’t depend on a specific server version of zk
----
2019-10-15 00:20:13 UTC - Sijie Guo: You can use zk 3.5+
----
2019-10-15 03:36:22 UTC - suigeneris84: @suigeneris84 has joined the channel
----
2019-10-15 07:19:56 UTC - hwangyungping: @hwangyungping has joined the channel
----
2019-10-15 08:32:45 UTC - 897068985: @897068985 has joined the channel
----