Master node Full disk

[#1]

after configure Navigator Metadata Server Heap, i m trying to restart Cloudera Management Service but i can't .
I get :

 Cannot restart service when Host Monitor (master) is in STOPPING state

In the Host Monitor log file :

mars 29, 14:05:55.133	ERROR	com.cloudera.cmon.firehose.Main	
Could not fetch descriptor after 5 tries, exiting.

and the number of files mgmt_mgmt-NAVIGATORMETASERVER*  increased

[#2]

@ghandrisaleh,

Please start a new thread for the issue trying to restart Host Monitor as this is not related to the existing one.

Restarting the Host Monitor is not required for restarting Navigator.  In Cloudera Manager, click on Clusters --> Cloudera Management Service

Then, click the "Instances" subtab

check the boxes beside the Navigator server you want to restart and choose "restart" from the Actions for Selected drop-down button.

This allows you to restart the roles you desire only.

[#3]

I do not know why the number of files mgmt_mgmt-NAVIGATORMETASERVER* increases

mgmt_mgmt-NAVIGATORMETASERVER-9a89af62abe8393b48c78926720ffe2c_pid19656.hprof

Despite that I have increased java heap size

[#4]

Hi,
What do your Navigator logs say? The log files will tell you why the server
crashed. What did you set the heap size to?

Regards,
Jim

[#5]

I increase the heap size by 1GB.
and cloudera work fine

[#6]

Now cloudera work Fine but in Host Monitor log file I get an error :

Could not fetch descriptor after 5 tries, exiting.

And i can't restart this service, and when i'm trying to restart the Cloudera Management Service i get :

Cannot restart service when Host Monitor (master) is in STOPPING state.

[#7]

Hi Jim,

Thanks for sharing the knowledge ,i just missed this point.
However from my past experience, we used to have lots of logs and lack in space due to the same above issue and to resolve it we stop navigator.
For my own curiosity, I would like to know what will be the impact on cluster if I stop navigator ?

[#8]

Hi,

Cloudera Navigator provides auditing and data management. Removing it will not stop you from being able to run jobs on your cluster but you will not have fine grained auditing, metadata tagging etc.

Regards,

Jim