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

zhengchenyu created HADOOP-18692: Summary: User in staticPriorities cost also shouldn't be accumulated to totalDecayedCallCost and totalRawCallCost. Key: HADOOP-18692 URL:

[jira] [Created] (HADOOP-18433) Fix main thread name.

zhengchenyu created HADOOP-18433: Summary: Fix main thread name. Key: HADOOP-18433 URL: https://issues.apache.org/jira/browse/HADOOP-18433 Project: Hadoop Common Issue Type: Improvement

[jira] [Updated] (HADOOP-18263) Prometheus metrics tag changed unexpectedly.

[ https://issues.apache.org/jira/browse/HADOOP-18263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhengchenyu updated HADOOP-18263: - Remaining Estimate: 336h Original Estimate: 336h > Prometheus metrics tag changed

[jira] [Commented] (HADOOP-18263) Prometheus metrics tag changed unexpectedly.

[ https://issues.apache.org/jira/browse/HADOOP-18263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17542466#comment-17542466 ] zhengchenyu commented on HADOOP-18263: -- PrometheusMetricsSink is introduced by HADOOP-16398, and

[jira] [Created] (HADOOP-18263) Prometheus metrics tag changed unexpectedly.

zhengchenyu created HADOOP-18263: Summary: Prometheus metrics tag changed unexpectedly. Key: HADOOP-18263 URL: https://issues.apache.org/jira/browse/HADOOP-18263 Project: Hadoop Common Issue

[jira] [Updated] (HADOOP-18263) Prometheus metrics tag changed unexpectedly.

[ https://issues.apache.org/jira/browse/HADOOP-18263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhengchenyu updated HADOOP-18263: - Description: Prom web print metrics like below {code:java}

[jira] [Issue Comment Deleted] (HADOOP-16254) Add proxy address in IPC connection

[ https://issues.apache.org/jira/browse/HADOOP-16254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhengchenyu updated HADOOP-16254: - Comment: was deleted (was: long time so that forget it. I repair HADOOP-16254.004.patch,

[jira] [Commented] (HADOOP-16254) Add proxy address in IPC connection

[ https://issues.apache.org/jira/browse/HADOOP-16254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17195299#comment-17195299 ] zhengchenyu commented on HADOOP-16254: -- long time so that forget it. I repair

[jira] [Commented] (HADOOP-16254) Add proxy address in IPC connection

[ https://issues.apache.org/jira/browse/HADOOP-16254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17144978#comment-17144978 ] zhengchenyu commented on HADOOP-16254: -- May I take over this issue, or we fix it together？ I think 

[jira] [Commented] (HADOOP-16254) Add proxy address in IPC connection

[ https://issues.apache.org/jira/browse/HADOOP-16254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17125736#comment-17125736 ] zhengchenyu commented on HADOOP-16254: -- I use RpcRequestHeaderProto to pass proxyAddress, then

[jira] [Commented] (HADOOP-16254) Add proxy address in IPC connection

[ https://issues.apache.org/jira/browse/HADOOP-16254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17125543#comment-17125543 ] zhengchenyu commented on HADOOP-16254: -- Additionally, InetSocketAddress is not proper. When set 

[jira] [Commented] (HADOOP-16254) Add proxy address in IPC connection

[ https://issues.apache.org/jira/browse/HADOOP-16254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17125541#comment-17125541 ] zhengchenyu commented on HADOOP-16254: -- I debug the code use HADOOP-16254.004.patch. But I found

[jira] [Commented] (HADOOP-16254) Add proxy address in IPC connection

[ https://issues.apache.org/jira/browse/HADOOP-16254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17123603#comment-17123603 ] zhengchenyu commented on HADOOP-16254: -- For security problem, I think this methods looks like

[jira] [Commented] (HADOOP-13909) Add serviceRestart function to the class AbstractService so that we could hot start some service or thread.

[ https://issues.apache.org/jira/browse/HADOOP-13909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15760038#comment-15760038 ] zhengchenyu commented on HADOOP-13909: -- I just code by your way. I called stop(), added a new

[jira] [Issue Comment Deleted] (HADOOP-13909) Add serviceRestart function to the class AbstractService so that we could hot start some service or thread.

[ https://issues.apache.org/jira/browse/HADOOP-13909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] zhengchenyu updated HADOOP-13909: - Comment: was deleted (was: I just code by your way. I called stop(), added a new instance. Then

[jira] [Commented] (HADOOP-13909) Add serviceRestart function to the class AbstractService so that we could hot start some service or thread.

[ https://issues.apache.org/jira/browse/HADOOP-13909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15760036#comment-15760036 ] zhengchenyu commented on HADOOP-13909: -- I just code by your way. I called stop(), added a new

[jira] [Created] (HADOOP-13909) Add serviceRestart function to the class AbstractService so that we could hot start some service or thread.

zhengchenyu created HADOOP-13909: Summary: Add serviceRestart function to the class AbstractService so that we could hot start some service or thread. Key: HADOOP-13909 URL: