You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Steven Lu (Jira)" <ji...@apache.org> on 2020/01/18 09:11:00 UTC

[jira] [Created] (KAFKA-9452) Add new cached authorizer:change the dim of cache

Steven Lu created KAFKA-9452:
--------------------------------

             Summary: Add new cached authorizer:change the dim of cache
                 Key: KAFKA-9452
                 URL: https://issues.apache.org/jira/browse/KAFKA-9452
             Project: Kafka
          Issue Type: Improvement
          Components: security
            Reporter: Steven Lu


Same like issues https://issues.apache.org/jira/browse/KAFKA-5261 ,

We met the same performance issue which is descripted in the pr [#3756|https://github.com/apache/kafka/pull/3756] in our production environment,hence, we make a revision for the mechamisum of authorization, our revision have such optimizations

1、Build a cache for authorization, which can avoid recomputation of authorization result. The authorization result will fetch on the result catch if the same result has been computed rather than compute it again
2、Differ from the pr 3756, when we build the result cache of the authorization, we take the resource into first consideration. In this way, the authorization is recomputed only when the authorization are change of specific resource. Compared to the the frequency of recomputation can be reduced obviously.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)