HaraldGustafsson commented on issue #2952: Setting topic permission under load URL: https://github.com/apache/pulsar/issues/2952#issuecomment-450412778 I understand the reasoning, but from the api it is not obvious that when you change permissions on different topics in the same namespace that you could get this concurrent conflict (and should retry), if you don't know that all topics permissions are stored in the namespace. At least I did not know it before digging a bit deeper. When realising this I needed to queue such operations on the client side and add retry since multiple workers might attempt to do changes. So when setting up many topics, with several configurations like retention, ttl, permissions, etc, they all need to be queued, and get rtt delay. In my setup, for each admin request we get we need to queue around 10 admin requests to pulsar, with retries even more. Would it be possible to introduce a larger namespace policy update method to change multiple things simultaneously, since in my case the conflict was often due to changing several things in the ns policy. On Fri, 28 Dec 2018, 19:49 Sijie Guo <[email protected] wrote: > @HaraldGustafsson <https://github.com/HaraldGustafsson> At the time of > bad version happening, it means there are concurrent updates to namespace > policy. It is hard to determine what is the real conflict and what conflict > it is. so returning CONFLICT status code sounds a right approach to me. > IMO, Pulsar applications which are using pulsar admin api should be able to > catch this exception and retries, because pulsar applications are better > places to resolve the conflict. Does that align with what you are thinking? > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <https://github.com/apache/pulsar/issues/2952#issuecomment-450408555>, or mute > the thread > <https://github.com/notifications/unsubscribe-auth/ADKqXf-Nb3u2i7X88mY23dJtaugbUCD_ks5u9metgaJpZM4YSXhe> > . >
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
