[jira] [Updated] (HDFS-17478) FSPermissionChecker to avoid obtaining a new AccessControlEnforcer instance before each authz call

2024-04-18 Thread Wei-Chiu Chuang (Jira)


 [ 
https://issues.apache.org/jira/browse/HDFS-17478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Wei-Chiu Chuang updated HDFS-17478:
---
Fix Version/s: 3.5.0
   (was: 3.4.1)

> FSPermissionChecker to avoid obtaining a new AccessControlEnforcer instance 
> before each authz call
> --
>
> Key: HDFS-17478
> URL: https://issues.apache.org/jira/browse/HDFS-17478
> Project: Hadoop HDFS
>  Issue Type: Improvement
>  Components: namanode
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
>Priority: Major
>  Labels: pull-request-available
> Fix For: 3.5.0
>
> Attachments: HDFS-17478.patch
>
>
> An instance of AccessControlEnforcer is obtained from the registered 
> INodeAttributeProvider before every call made to authorizer. This can be 
> avoided by initializing the AccessControlEnforcer instance during 
> construction of FsPermissionChecker and using it in every subsequent call to 
> the authorizer. This will eliminate the unnecessary overhead in highly 
> performance sensitive authz code path.
>  
> CC: [~abhay], [~arp], [~swagle]



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org



[jira] [Updated] (HDFS-17478) FSPermissionChecker to avoid obtaining a new AccessControlEnforcer instance before each authz call

2024-04-18 Thread Wei-Chiu Chuang (Jira)


 [ 
https://issues.apache.org/jira/browse/HDFS-17478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Wei-Chiu Chuang updated HDFS-17478:
---
Fix Version/s: 3.4.1
   Resolution: Fixed
   Status: Resolved  (was: Patch Available)

> FSPermissionChecker to avoid obtaining a new AccessControlEnforcer instance 
> before each authz call
> --
>
> Key: HDFS-17478
> URL: https://issues.apache.org/jira/browse/HDFS-17478
> Project: Hadoop HDFS
>  Issue Type: Improvement
>  Components: namanode
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
>Priority: Major
>  Labels: pull-request-available
> Fix For: 3.4.1
>
> Attachments: HDFS-17478.patch
>
>
> An instance of AccessControlEnforcer is obtained from the registered 
> INodeAttributeProvider before every call made to authorizer. This can be 
> avoided by initializing the AccessControlEnforcer instance during 
> construction of FsPermissionChecker and using it in every subsequent call to 
> the authorizer. This will eliminate the unnecessary overhead in highly 
> performance sensitive authz code path.
>  
> CC: [~abhay], [~arp], [~swagle]



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org



[jira] [Updated] (HDFS-17478) FSPermissionChecker to avoid obtaining a new AccessControlEnforcer instance before each authz call

2024-04-17 Thread ASF GitHub Bot (Jira)


 [ 
https://issues.apache.org/jira/browse/HDFS-17478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated HDFS-17478:
--
Labels: pull-request-available  (was: )

> FSPermissionChecker to avoid obtaining a new AccessControlEnforcer instance 
> before each authz call
> --
>
> Key: HDFS-17478
> URL: https://issues.apache.org/jira/browse/HDFS-17478
> Project: Hadoop HDFS
>  Issue Type: Improvement
>  Components: namanode
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
>Priority: Major
>  Labels: pull-request-available
> Attachments: HDFS-17478.patch
>
>
> An instance of AccessControlEnforcer is obtained from the registered 
> INodeAttributeProvider before every call made to authorizer. This can be 
> avoided by initializing the AccessControlEnforcer instance during 
> construction of FsPermissionChecker and using it in every subsequent call to 
> the authorizer. This will eliminate the unnecessary overhead in highly 
> performance sensitive authz code path.
>  
> CC: [~abhay], [~arp], [~swagle]



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org



[jira] [Updated] (HDFS-17478) FSPermissionChecker to avoid obtaining a new AccessControlEnforcer instance before each authz call

2024-04-17 Thread Madhan Neethiraj (Jira)


 [ 
https://issues.apache.org/jira/browse/HDFS-17478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Madhan Neethiraj updated HDFS-17478:

Description: 
An instance of AccessControlEnforcer is obtained from the registered 
INodeAttributeProvider before every call made to authorizer. This can be 
avoided by initializing the AccessControlEnforcer instance during construction 
of FsPermissionChecker and using it in every subsequent call to the authorizer. 
This will eliminate the unnecessary overhead in highly performance sensitive 
authz code path.

 

CC: [~abhay], [~arp], [~swagle]

  was:An instance of AccessControlEnforcer is obtained from the registered 
INodeAttributeProvider before every call made to authorizer. This can be 
avoided by initializing the AccessControlEnforcer instance during construction 
of FsPermissionChecker and using it in every subsequent call to the authorizer. 
This will eliminate the unnecessary overhead in highly performance sensitive 
authz code path.


> FSPermissionChecker to avoid obtaining a new AccessControlEnforcer instance 
> before each authz call
> --
>
> Key: HDFS-17478
> URL: https://issues.apache.org/jira/browse/HDFS-17478
> Project: Hadoop HDFS
>  Issue Type: Improvement
>  Components: namanode
>Reporter: Madhan Neethiraj
>Assignee: Madhan Neethiraj
>Priority: Major
> Attachments: HDFS-17478.patch
>
>
> An instance of AccessControlEnforcer is obtained from the registered 
> INodeAttributeProvider before every call made to authorizer. This can be 
> avoided by initializing the AccessControlEnforcer instance during 
> construction of FsPermissionChecker and using it in every subsequent call to 
> the authorizer. This will eliminate the unnecessary overhead in highly 
> performance sensitive authz code path.
>  
> CC: [~abhay], [~arp], [~swagle]



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org



[jira] [Updated] (HDFS-17478) FSPermissionChecker to avoid obtaining a new AccessControlEnforcer instance before each authz call

2024-04-17 Thread Madhan Neethiraj (Jira)


 [ 
https://issues.apache.org/jira/browse/HDFS-17478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Madhan Neethiraj updated HDFS-17478:

Attachment: HDFS-17478.patch
Status: Patch Available  (was: Open)

> FSPermissionChecker to avoid obtaining a new AccessControlEnforcer instance 
> before each authz call
> --
>
> Key: HDFS-17478
> URL: https://issues.apache.org/jira/browse/HDFS-17478
> Project: Hadoop HDFS
>  Issue Type: Improvement
>  Components: namanode
>Reporter: Madhan Neethiraj
>Priority: Major
> Attachments: HDFS-17478.patch
>
>
> An instance of AccessControlEnforcer is obtained from the registered 
> INodeAttributeProvider before every call made to authorizer. This can be 
> avoided by initializing the AccessControlEnforcer instance during 
> construction of FsPermissionChecker and using it in every subsequent call to 
> the authorizer. This will eliminate the unnecessary overhead in highly 
> performance sensitive authz code path.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org