2020-09-04 09:36:53 UTC - otman: @otman has joined the channel ---- 2020-09-04 10:11:59 UTC - otman: Hi all, quick questions. i face an issue on apache pulsar 2.6.1. My java program is also using same version number and sometime i face following exception: ```Failed to subscribe for topic [<persistent://xxxxx/agent_xx/event-967b12df-cd08-4467-a31d-9a38928f0727>] in topics consumer java.lang.IllegalStateException: allTopicPartitionsNumber 124 not equals expected: 123``` My programe subscribe on a topic pattern. It succesfully subscribed and then exception is throw and consumer closed. Did someone face this issue ? ---- 2020-09-04 14:52:50 UTC - Ebere Abanonu: For the Microsoft azure folks <!here>, I have created a little demo on how to deploy Pulsar on Azure and use <https://github.com/eaba/SharpPulsar> with SignalR, Aspnet Core Web API and Angular here: <https://github.com/eaba/SharpPulsarSamples> ---- 2020-09-04 14:53:36 UTC - Ebere Abanonu: Am available to offer more............ ---- 2020-09-04 14:53:42 UTC - Mark Marijnissen: please don't ping 2225 people with the @here tag if it's not urgent, thank you +1 : Fabien LD ---- 2020-09-04 14:56:24 UTC - Ebere Abanonu: Am only notifying every body so that those who it is meant for or need it, don't miss it - broadcast! I understand your concern, see me point of view! ---- 2020-09-04 15:16:57 UTC - Chris: I've been seeing this issue pop up recently too even with small numbers of topics. I increased the concurrent lookup count to 150k which I think just causes timeouts instead. Metrics say 99% zk response times are ~20 ms at worst, so I don't think it's those? ---- 2020-09-04 15:18:56 UTC - Chris: Broker restarts usually fix the issue for a while for me, so my guess is something is getting stuck in the lookup queue somehow. If we don't yet have an issue for this I'll open one on monday or so, but I'd really like to have more information to go on than "this is broken and I don't think it's me". +1 : Lari Hotari ---- 2020-09-04 16:06:57 UTC - Addison Higham: @Ebere Abanonu we do have some conventions we try and follow in the community to not use the @ here tag as it can be disruptive, so if you could please help us by following that best practice, it would be really helpful.
This is a useful contribution and I think we as a community can improve to find a place where to post these sorts of useful resources so that others don't miss it but in a way that isn't seen as disruptive. I hope you can understand that as the community grows, we need to be careful about effectively using our tools so it never gets to a point of people feeling overwhelmed being in this channel. Here are a few ideas I think we could try out: - we could create a new slack channel like `#community_annoucements` and would be a good place to share these sorts of things - StreamNative has a weekly update we send out: <https://streamnative.io/weekly> and we could add it there - We can work to get some of the existing channels, like <#CUAMT2NJE|dev-dotpulsar> to have more visibility so that the interested parties join there where they can get more direct communication ---- 2020-09-04 16:13:00 UTC - Ruian: Hi, is there an API for the partition reader/consumer to get how far its current position behind the latest message? ---- 2020-09-04 16:16:28 UTC - Fabien LD: Maybe if we are 2225 pinging @Ebere Abanonu at different time during the next 24h then it will make it clear that being interrupted by a Slack notification is maybe not the most pleasant thing ---- 2020-09-04 18:07:17 UTC - Ebere Abanonu: @Fabien LD I won't have problem with that after all we all get thousands of WhatsApp, Twitter, GitHub notifications and how do we handle it? ---- 2020-09-04 18:11:57 UTC - Ebere Abanonu: Telling individuals to sort of "shut up" will be demoralizing. @Addison Higham that need to be worked out...because if I have worked really hard at something, then it follows I broadcast it by myself or by the community. ---- 2020-09-04 18:12:33 UTC - Ebere Abanonu: Support can be mutual..... ---- 2020-09-04 18:20:14 UTC - Evan Furman: ---- 2020-09-04 18:20:36 UTC - Addison Higham: certainly, we want to make sure we have a good place to highlight contributions in the community as they are very valuable! I think we can definitely work on making that better. We need your and others help to do that. But at the same time you have to have patience with us as we develop those new channels of communication while also respecting the existing standards in the community. ---- 2020-09-04 18:21:16 UTC - Frank Kelly: Perhaps a silly question but what is the purpose of these `Thread.sleep(3000)` calls in this Test Class - is the Policy persistence to ZooKeeper asynchronous? <https://github.com/apache/pulsar/blob/2e88fdb9c3fb67e5e7d2f67ad075c114c6a60358/pulsar-broker/src/test/java/org/apache/pulsar/broker/admin/TopicPoliciesTest.java#L73> ---- 2020-09-04 18:22:00 UTC - Addison Higham: otherwise, we risk pushing people away from the community rather than growing it collaboratively +1 : Fabien LD ---- 2020-09-04 18:25:50 UTC - Ebere Abanonu: Am with you @Addison Higham ---- 2020-09-04 18:28:05 UTC - Addison Higham: :bow: thanks for understanding and as I mentioned, I think we can figure out a few of those things pretty quick. On my side, I can ask around about having a "community contributions" section as part of the weekly update and I will get some conversations started about an announcements channel ---- 2020-09-04 18:30:35 UTC - Addison Higham: the actual writing of the policy to ZK is immediate, but some of the changes that happen internally in responses to policy changes are not. I am not sure what the specific ones would be in this case. Obviously sleeps aren't ideal and is an area where we could make some improvements ---- 2020-09-04 18:31:52 UTC - Frank Kelly: Thanks - so it sounds like there is some poller or other async reader of policies? ---- 2020-09-04 18:36:16 UTC - Addison Higham: yes, there are ZK watches set up against policies that perform actions (usually invalidating local caches) ---- 2020-09-04 18:36:30 UTC - Frank Kelly: Cool - Thanks ---- 2020-09-04 18:38:14 UTC - Addison Higham: if you want to see the most important one: <https://github.com/apache/pulsar/blob/d4a1ca59dafa1a8f4050bbaa442543250f789bf2/pulsar-broker/src/main/java/org/apache/pulsar/broker/service/persistent/PersistentTopic.java#L1787> ---- 2020-09-04 18:38:24 UTC - Addison Higham: err, most likely to be involved in that test ---- 2020-09-04 18:38:59 UTC - Addison Higham: as part of the top level consumer API I don't believe so but I think you could probably call `pulsar-admin topics stats` and get some of that data as that has info on consumers ---- 2020-09-04 18:39:15 UTC - Frank Kelly: Awesome - thanks so much! I have it bookmarked as I'm sure I'll need it again :slightly_smiling_face: ---- 2020-09-04 18:41:38 UTC - Addison Higham: (hot take idea on making the testing better: we should introduce a "hook" in those zk watches to see when they complete and then know we are safe to proceed with tests) ---- 2020-09-04 18:43:06 UTC - Frank Kelly: For sure! :slightly_smiling_face: ---- 2020-09-04 19:49:42 UTC - Stepan Mazurov: there is actually, just found it: <https://github.com/streamnative/terraform-provider-pulsar> ---- 2020-09-04 20:16:53 UTC - Evan Furman: Will this work @Sijie Guo? ----
