This test verifies that if the monitor service is shut down the fail over is not triggered. The NameNode can now be manipulated as part of planned management operations.
Start the NameNode VM and SSH to the NameNode VM.
Terminate the monitor process.
service hmonitor-namenode-monitor stop
Note A kill -9 command for the monitor is not a graceful shutdown and will trigger fail over.
Terminate the NameNode process.
service hadoop-namenode stop
Ensure that you see the following expected results:
In the vSphere Management UI, the NameNode VM should be live.
The fail over should not be initiated by vSphere.
In HAM, the NameNode status area should indicate offline status. The non-blocking operations should now report failure.
The SSH connection must not be broken and the VM should be live.
Restart the monitor process.
service hmonitor-namenode-monitor start
Restart the NameNode process.
service hadoop-namenode start
The NameNode health should be monitored and failures should trigger fail over.