2020-09-09 09:55:25 UTC - Gabriel Volpe: Any maintainer here that can review and hopefully merge this small PR? ---- 2020-09-09 09:55:27 UTC - Gabriel Volpe: <https://github.com/apache/pulsar/pull/7992> ---- 2020-09-09 10:02:49 UTC - Ali Ahmed: @Gabriel Volpe approved ---- 2020-09-09 10:03:21 UTC - Gabriel Volpe: thanks for the quick response! ---- 2020-09-09 10:25:19 UTC - Seun: How best can one get Apache pulsar running on spinnaker via helm charts? ---- 2020-09-09 12:25:04 UTC - Jim M.: Are there any docs/guides to tune pulsar? in addition, is there a way to set partitions on a topic by producer or consumer or programmatically, can't see to find documentation on that ---- 2020-09-09 13:13:34 UTC - Allen ONeill: Interesting analysis here of the Pulsar codebase!
<https://dzone.com/articles/looking-under-the-hood-of-apache-pulsar-how-good-i> ---- 2020-09-09 15:41:35 UTC - Seun: Anybody knows how to troubleshoot this? `Warning FailedScheduling pod/pulsar-zookeeper-1 error while running "VolumeBinding" filter plugin for pod "pulsar-zookeeper-1": pod has unbound immediate PersistentVolumeClaims` `Warning FailedScheduling pod/pulsar-zookeeper-2 error while running "VolumeBinding" filter plugin for pod "pulsar-zookeeper-2": pod has unbound immediate PersistentVolumeClaims` `seun@seun:~/pulsar/pulsar$ kubectl -n spinnaker get events --sort-by='{.lastTimestamp}' | grep -i error` ---- 2020-09-09 15:42:19 UTC - Seun: Environment is GKE running inside Spinnaker. ---- 2020-09-09 18:37:36 UTC - Harel Ben-Attia: @Harel Ben-Attia has joined the channel ---- 2020-09-09 22:35:06 UTC - Rolf Arne Corneliussen: AUTHENTICATION question: I have two Pulsar clusters in different regions, and I want to set up replication between clusters. I want the replication client to use TLS with client cert authentication to authenticate with a Pulsar Proxy that sits in front of the Pulsar cluster in the other region. Initially, I did not set up any authentication between the Pulsar Proxy and the Pulsar nodes behind it (on private network), but the replication client would not pick up the client certificate given in '`brokerClientAuthenticationParameter`' UNLESS I also enabled authentication of incoming request to the broker (`authenticationEnabled`). Question 1: Is there some good reason for this behavior? Should there be a separate authentication configuration for the replication client? Question 2: I did set up token based authentication between the Pulsar Proxy and the brokers, and it works as expected with replication (TLS client authentication to the proxy, token authentication from proxy to broker), but if a broker wants to talk to a peer broker within the same cluster, I guess it will fail if it uses `brokerClientAuthenticationPlugin` and `brokerClientAuthenticationParameter` settings (TLS). I have not seen anything in the logs, but will a Pulsar broker ever try to communicate directly with a peer broker, or do the brokers just use ZooKeeper to coordinate themselves? ---- 2020-09-10 07:02:11 UTC - Shivji Kumar Jha: Where can i find offloaders for 2.5.2 ? Installed 2.5.2 but I can only find 2.6.1 offloaders on downloads page (<https://pulsar.apache.org/ko/download/>) ---- 2020-09-10 07:06:44 UTC - Shivji Kumar Jha: The 2.6.1 offloader doesnt work. It seems older version is not available at <http://mirror.metrocast.net/apache/pulsar/> ---- 2020-09-10 07:31:15 UTC - Penghui Li: <https://archive.apache.org/dist/pulsar/pulsar-2.5.2/> +1 : Shivji Kumar Jha ---- 2020-09-10 08:29:40 UTC - Ebere Abanonu: Generally, that error is about the inability to create a persistent volume which could be due to improper or lack of StorageClass. So create a StorageClass and in the Helm Charts Values.yaml look for storage class name and set that to the name of the StorageClass you created ---- 2020-09-10 08:32:12 UTC - Ebere Abanonu: At times if the StorageClass does exists then you will have to give it some time to bound ----
