2019-11-13 10:48:58 UTC - Pedro Cardoso: Has anyone come across a similar stack trace when trying to trigger pulsar functions? ---- 2019-11-13 11:23:23 UTC - Sijie Guo: looks like your function didn’t run. so the health check between function worker and function failed.
you can take a look at the function log. ---- 2019-11-13 11:55:59 UTC - Pedro Cardoso: How can I find the function log in a k8s environment? ---- 2019-11-13 12:15:35 UTC - Kabeer Ahmed: Hello, I am looking to do the below: ---- 2019-11-13 12:16:05 UTC - Kabeer Ahmed: Consume from multiple topics in Pulsar and Write them to distinct S3 locations. ---- 2019-11-13 12:16:21 UTC - Kabeer Ahmed: Kafka Connect does this by default. Is there a way that I can efficiently do this? ---- 2019-11-13 12:16:50 UTC - Kabeer Ahmed: Or other ideas that could help me do this efficiently? I do not want to reinvent the wheel if Pulsar Connect or any other tool might be doing this job automatically ---- 2019-11-13 14:03:31 UTC - Igor Zubchenok: any update @Sijie Guo? ---- 2019-11-13 14:04:15 UTC - Igor Zubchenok: any update @Sijie Guo @Matteo Merli? ---- 2019-11-13 15:54:23 UTC - Retardust: - ---- 2019-11-13 16:00:42 UTC - Retardust: the throughput remains low even after "warm up" of most producers ---- 2019-11-13 16:26:52 UTC - Retardust: my mistake ---- 2019-11-13 19:16:31 UTC - Naveen Kumar: Is it possible to set compressionType in pulsar topic level instead of producer compressionType? ---- 2019-11-13 19:32:01 UTC - Matteo Merli: Not really, because the data is compressed directly in the client side ---- 2019-11-14 00:22:42 UTC - Sijie Guo: Pulsar IO should have the same ability to do so. Although I don’t think we have an S3 sink available in the main repo, it should be straightforward to implement one ---- 2019-11-14 00:24:36 UTC - Sijie Guo: It is under logs dir. logs/functions/<tenant>/<namespace>/<name> ---- 2019-11-14 05:46:58 UTC - Viji: We are currently using Pulsar 2.4.1. We need the fix related to the PR <https://github.com/apache/pulsar/commit/6a67ae094b5ecfa1a4602b8f7baff9a838b44e23#diff-d4876cc56bcbd7b0fe549311203cd213>. Which can we expect the stable release with above fix ? ---- 2019-11-14 05:48:24 UTC - Viji: We are currently using Pulsar 2.4.1. We need the fix related to the PR <https://github.com/apache/pulsar/commit/6a67ae094b5ecfa1a4602b8f7baff9a838b44e23#diff-d4876cc56bcbd7b0fe549311203cd213>. Which can we expect the stable release with above fix ? ---- 2019-11-14 06:32:13 UTC - Sijie Guo: I marked that as for 2.4.2. so it can go out with the 2.4.2 release, which will happen this week or next week. ---- 2019-11-14 06:32:25 UTC - Sijie Guo: ^ @xiaolong.ran: <https://github.com/apache/pulsar/pull/5068> ---- 2019-11-14 06:33:20 UTC - xiaolong.ran: ok ---- 2019-11-14 06:55:55 UTC - Rahul Vashishth: @Rahul Vashishth has joined the channel ---- 2019-11-14 07:15:16 UTC - Viji: Thanks !! ----
