[
https://issues.apache.org/jira/browse/HADOOP-13909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15751652#comment-15751652
]
Steve Loughran commented on HADOOP-13909:
-----------------------------------------
hmm. This is fairly hard to pull off. What would be easier would be to detach a
child of a composite service, stop it, then add a new instance if the same
service.
As usual, please set the affects versions & component fields. Thx.
> Add serviceRestart function to the class AbstractService so that we could hot
> start some service or thread.
> -----------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-13909
> URL: https://issues.apache.org/jira/browse/HADOOP-13909
> Project: Hadoop Common
> Issue Type: Wish
> Components: common
> Reporter: zhengchenyu
> Priority: Minor
> Original Estimate: 1m
> Remaining Estimate: 1m
>
> In our cluster, we found that the web service was not available, maybe jetty
> server didn't close the socket normally so that so many connection keep the
> state of CLOSE_WAIT. Here we decide to restart the resourcemanager, then
> problem is solved.But we must know other service of the resourcemanager is
> normal.
> In this case, we must restart the resourcemanager process, just because of
> web service. Other service is paused because of restarting resourcemanager,
> but other service is normal.
> Here I wish to add a serviceRestart function so that we could only restart
> the web service thread when web service is not normal. This operation won't
> influence other service.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
