Hi,

We are using MirrorMaker 2 (version 2.6.2 - to match our cluster version) to 
migrate applications from one cluster to another, and as such, need the topic 
ACLs to be the same on both clusters.  The ACLs are being replicated, but the 
operation is being set to "READ", even if the operation in the source cluster 
was "ALL" or "WRITE".

Here's an example ACL:

Old cluster -
Current ACLs for resource `ResourcePattern(resourceType=TOPIC, 
name=gms-price-logic-detail, patternType=LITERAL)`: 
(principal=User:CN=MirrorMaker_DEV, host=*, operation=ALL, permissionType=ALLOW)
(principal=User:CN=WGS_DEV, host=*, operation=ALL, permissionType=ALLOW)

New cluster -
Current ACLs for resource `ResourcePattern(resourceType=TOPIC, 
name=gms-price-logic-detail, patternType=LITERAL)`: 
(principal=User:CN=WGS_DEV, host=*, operation=READ, permissionType=ALLOW)
(principal=User:CN=MirrorMaker_DEV, host=*, operation=READ, 
permissionType=ALLOW) 

If I manually add an ALL ACL to a topic on the new cluster, MM2 will sooner or 
later add another READ ACL to that same topic, even though the ACLs now match.

Is there some hidden config value I'm missing?  I've verified in the logs that 
"sync.topic.acls.enabled" is set to true.

Thanks,
Alex
**

Reply via email to