[jira] [Created] (HADOOP-18691) Add a CallerContext getter on the Schedulable interface

2023-04-06 Thread Christos Bisias (Jira)
Christos Bisias created HADOOP-18691:


 Summary: Add a CallerContext getter on the Schedulable interface
 Key: HADOOP-18691
 URL: https://issues.apache.org/jira/browse/HADOOP-18691
 Project: Hadoop Common
  Issue Type: Improvement
Reporter: Christos Bisias


We would like to add a default CallerContext getter on the Schedulable interface
{code:java}
default public CallerContext getCallerContext() {
  return null;  
} {code}
and then override it on the ipc/Server.Call class
{code:java}
@Override
public CallerContext getCallerContext() {  
  return this.callerContext;
} {code}
to expose the already existing callerContext field.

 

This change will help us access the CallerContext on an Apache Ozone 
IdentityProvider implementation.

On Ozone side the FairCallQueue doesn't work with the Ozone S3G, because all 
users are masked under a special S3G user and there is no impersonation. 
Therefore, the FCQ reads only 1 user and becomes ineffective. We can use the 
CallerContext field to store the current user and access it on the Ozone 
IdentityProvider.

 

This is a presentation with the proposed approach.

https://docs.google.com/presentation/d/1iChpCz_qf-LXiPyvotpOGiZ31yEUyxAdU4RhWMKo0c0/edit#slide=id.p



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

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



[jira] [Created] (HADOOP-18663) DecayRpcSchedulerDetailedMetrics display name numbers incremented by 1

2023-03-14 Thread Christos Bisias (Jira)
Christos Bisias created HADOOP-18663:


 Summary: DecayRpcSchedulerDetailedMetrics display name numbers 
incremented by 1
 Key: HADOOP-18663
 URL: https://issues.apache.org/jira/browse/HADOOP-18663
 Project: Hadoop Common
  Issue Type: Bug
Reporter: Christos Bisias


It should keep names consistent with 
{color:#00875a}DecayRpcSchedulerMetrics{color}, to avoid confusion.


What might be displayed as Priority.0 and Priority.1 for 
{color:#00875a}DecayRpcSchedulerMetrics{color}, it's Priority.1 and Priority.2 
for {color:#00875a}DecayRpcSchedulerDetailedMetrics{color}.



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

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