2020-07-21 09:32:12 UTC - Nhat Ha Trinh: @Sijie Guo, I have an issue when compression is set to 'snappy' and batching is enabled with pulsar-client 2.5.0. I also found a similar ticket in github(<https://github.com/apache/pulsar/pull/6375>). Could you please let me know the solution to fix this issue with pulsar-client 2.5.0? ---- 2020-07-21 09:34:13 UTC - Sijie Guo: The fix is available in 2.5.1 and 2.6.0 ---- 2020-07-21 09:34:46 UTC - Nhat Ha Trinh: But do you have any solution for 2.5.0? ---- 2020-07-21 09:37:31 UTC - Sijie Guo: Unfortunately, there is no solution for 2.5.0. You have to upgrade the client to 2.5.1. 2.5.1 is a bugfix release for 2.5.0 ---- 2020-07-21 09:38:00 UTC - Nhat Ha Trinh: ok. thank you ---- 2020-07-21 12:09:04 UTC - Arthur: I don't understand the behaviour of the stat api of pulsar (/admin/v2/broker-stats/topics). It's seems if I call it two times, it returns nothing the second times, is it normal? Putting statsUpdateFrequencyInSecs=30 and statsUpdateInitialDelayInSecs=30 doesn't change anything. Last point, I disconnect a pulsar client, I expect stat api to return me this change of status immediatly but I have to wait 3 minutes! Is it expected? ---- 2020-07-21 13:24:10 UTC - Shivji Kumar Jha: @Addison Higham Got this one working. Thanks for you help! ---- 2020-07-21 13:35:24 UTC - Nhat Ha Trinh: @Sijie Guo, I have tried pulsar-client 2.6.0 with compression = snappy and E2E. But it failed with Pulsar Encryption same as this issue <https://github.com/apache/pulsar/issues/6834> ---- 2020-07-21 13:36:24 UTC - Nhat Ha Trinh: I also have tried pulsar-client 2.5.2 and it works. I think the bytebuff fix is not in 2.6.0 ---- 2020-07-21 14:51:24 UTC - Jorge Miralles: Hi guys! Hope you’re doing well! I have a question about peeking encrypted messages: We’ve been using pulsar client (java) to peek messages, but now that we’re encrypting them, message peeking seems to be failing. I’ve read the docs but couldn’t find anything about it.
We’ve seen errors like this when trying to peek messages: Caused by: org.apache.pulsar.client.admin.PulsarAdminException$ServerSideErrorException: Some error occourred on the server Is there a way to decrypt messages in java client for peeking? ---- 2020-07-21 17:10:10 UTC - Addison Higham: oh good! what was the fix @Shivji Kumar Jha? ---- 2020-07-21 17:25:14 UTC - alex kurtser: Hello. Is there an ability to monitor connections to pulsar (via proxy)? I mean , that we would like to know who is connected to pulsar , at least client's source IP and probably other details , like authentication details and so on. ---- 2020-07-22 00:11:14 UTC - Hiroyuki Yamada: @Penghui Li How is it going ? Sorry for pushing, but It would be great if you can answer my questions. <https://github.com/apache/pulsar/issues/7455#issuecomment-654763271> I need to understand the current strategy so that I can dig into it a bit more easily. ---- 2020-07-22 02:41:47 UTC - Shivji Kumar Jha: @Addison Higham We moved from bookkeeper certifying every client under *.<http://beam.com|beam.com> to explicitly adding all broker client certs to all bookie trustores. Now when broker comes calling, its cert is already present as a trusted client. ---- 2020-07-22 02:46:55 UTC - Ryan: What is the status of large message chunking? ---- 2020-07-22 02:59:54 UTC - Addison Higham: @Ryan it is released in 2.6.0, see <https://github.com/apache/pulsar/pull/4400/> or <https://pulsar.apache.org/blog/2020/06/18/Apache-Pulsar-2-6-0/#pip-37-large-message-size-support> for the PR. One thing to note: it only works for non-shared subscriptions +1 : Ryan ---- 2020-07-22 03:29:32 UTC - lyuanlai: @lyuanlai has joined the channel ---- 2020-07-22 04:22:49 UTC - Ryan: I see, thank you, yes I was tracking PIP 37 but wasn't sure if it had been implemented or was waiting on transactional support and/or <https://github.com/streamnative/pulsar/issues/1045>. So large message support is now supported, but for Exclusive subscriptions only? Is there any plan to support Key_Shared subscriptions? ---- 2020-07-22 06:27:21 UTC - Rattanjot Singh: Hi. When try to run pulsar-admin commands on my standalone.I get. ```bin/pulsar-admin namespaces list public HTTP 401 Unauthorized Reason: HTTP 401 Unauthorized``` And i get this logs from standalone ```11:54:59.039 [pulsar-web-54-4] WARN org.apache.pulsar.broker.web.AuthenticationFilter - [127.0.0.1] Failed to authenticate HTTP request: http not supported 11:54:59.040 [pulsar-web-54-4] INFO org.eclipse.jetty.server.RequestLog - 127.0.0.1 - - [22/Jul/2020:11:54:59 +0530] "GET /admin/v2/namespaces/public HTTP/1.1" 401 0 "-" "Pulsar-Java-v2.6.0" 1``` Any ideas why I am getting this? I have used a custom Authentication class for this. ---- 2020-07-22 07:12:15 UTC - Penghui Li: @Hiroyuki Yamada I have comment in the issue, and now looks the problem is <https://github.com/apache/pulsar/pull/7553> that described. ---- 2020-07-22 08:00:27 UTC - Raghav: Hi, I want to run a performance test with ordered messages. In pulsar-perf tool are there any config variables that I can make use of to make sure ordering is preserved while producing the messages and verify the ordering in consumers? Also do the variables _*max-outstanding-across-partitions, max-outstanding, batch-max-messages*_ preserve ordering while producing ? ---- 2020-07-22 08:58:40 UTC - Vincent: @Vincent has joined the channel ----
