You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ambari.apache.org by "D M Murali Krishna Reddy (Jira)" <ji...@apache.org> on 2023/08/16 07:39:00 UTC

[jira] [Commented] (AMBARI-25950) Exclude hosts getting erased when RM, NN are restarted

    [ https://issues.apache.org/jira/browse/AMBARI-25950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17754916#comment-17754916 ] 

D M Murali Krishna Reddy commented on AMBARI-25950:
---------------------------------------------------

[~vjasani]  I just checked on the 2.6 based cluster and was not able to reproduce this issue. 
Looks this issue is induced by AMBARI-23493


Can you review the changes on the PR?

Thanks

> Exclude hosts getting erased when RM, NN are restarted
> ------------------------------------------------------
>
>                 Key: AMBARI-25950
>                 URL: https://issues.apache.org/jira/browse/AMBARI-25950
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>            Reporter: D M Murali Krishna Reddy
>            Assignee: D M Murali Krishna Reddy
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> After decommissioning a Node Manager or a Data node, if Resource Manager or Namenode are restarted, the exclude hosts file is getting overwritten with empty contents, causing the NM, DN to get recommisioned.
>  
> During NN, RM restart all_decommissioned_hosts is not set due to which in params_linux.py the exclude hosts file is getting created with empty content.



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

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