2019-11-18 15:56:19 UTC - Pedro Cardoso: @Pedro Cardoso has joined the channel ---- 2019-11-18 15:56:36 UTC - Pedro Cardoso: Is there a known workaround for <https://github.com/apache/pulsar/issues/5687>? ---- 2019-11-18 21:52:01 UTC - Addison Higham: hrm... have run into this a few times now: ``` pulsar-admin topics grant-permission <persistent://tenant/ns/topic--actions> consume --role myrole Concurrent modification
Reason: Concurrent modification ``` ---- 2019-11-18 21:52:16 UTC - Addison Higham: a broker restart doesn't appear to fix it ---- 2019-11-18 21:52:23 UTC - Addison Higham: logs don't show any sort of stack trace ---- 2019-11-18 22:12:33 UTC - David Kjerrumgaard: @Addison Higham Can you file an issue for this? Are there any specific steps to repro this issue? ---- 2019-11-18 22:13:21 UTC - Addison Higham: am digging in to figure out more info... might be our ZK cluster in a weird state... but using a ZK CLI, I don't see the version number changing... so that was weird ---- 2019-11-18 22:13:49 UTC - David Kjerrumgaard: Which version number? ---- 2019-11-18 22:23:36 UTC - Addison Higham: err so in this code, pulsar sends along a version number with an update (sort of like a compare-and-set) and the error appears to be caused when something else also changes that version number (hence concurrent modification) but we were getting the error every single time. Interestingly, after manually making a change to the policy in ZK (directly) I no longer saw the issue thinking_face : David Kjerrumgaard ---- 2019-11-18 22:23:42 UTC - Addison Higham: so... really not sure on that one :confused: ----
