[jira] [Created] (HADOOP-18692) User in staticPriorities cost also shouldn't be accumulated to totalDecayedCallCost and totalRawCallCost.

["zhengchenyu (Jira)" <ji...@apache.org>]

zhengchenyu created HADOOP-18692:
------------------------------------

             Summary: User in staticPriorities cost also shouldn't be accumulated to totalDecayedCallCost and totalRawCallCost.
                 Key: HADOOP-18692
                 URL: https://issues.apache.org/jira/browse/HADOOP-18692
             Project: Hadoop Common
          Issue Type: Improvement
          Components: common
            Reporter: zhengchenyu


After HADOOP-17165, we can avoid to restrict some important user who has many request.

In HADOOP-17346, the solution is similar to HADOOP-17165, but the user is service user. And another improvement in HADOOP-17346 is that we can avoid backoff by response time. 

HADOOP-17280 solve the problem "Service-user cost shouldn't be accumulated to totalDecayedCallCost and totalRawCallCost." for HADOOP-17165. HADOOP-17346 also fix it.

I think some code is redundancy, we should reconstruct. 



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

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org