-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/48708/
-----------------------------------------------------------

(Updated June 15, 2016, 9:55 a.m.)


Review request for Ambari, Alejandro Fernandez, Dmitro Lisnichenko, and Nate 
Cole.


Changes
-------

Updating tests and grammar.


Bugs: AMBARI-17236
    https://issues.apache.org/jira/browse/AMBARI-17236


Repository: ambari


Description
-------

When starting NN during an EU, we're hitting this when trying to create HDFS 
directories:
```
{
  "RemoteException": {
    "exception": "RetriableException", 
    "javaClassName": "org.apache.hadoop.ipc.RetriableException", 
    "message": "NameNode still not started"
  }
}
```

So, the heart of this issue is that, depending on topology and upgrade type, we 
might not wait for NN to be out of Safe Mode after starting. However, we are 
always creating directories, regardless of topology/upgrade:

```
    # Always run this on non-HA, or active NameNode during HA.
    if is_active_namenode:
      create_hdfs_directories()
      create_ranger_audit_hdfs_directories()
```

NameNode, in Safe Mode, is read-only and would forbid this anyway, even if it 
didn't throw a retryable exception:
```
[hdfs@c6403 root]$ hadoop fs -mkdir /foo
mkdir: Cannot create directory /foo. Name node is in safe mode.
```

So, it seems like we need to wait for NN to be out of Safe Mode no matter what.


Diffs (updated)
-----

  
ambari-common/src/main/python/resource_management/libraries/resources/hdfs_resource.py
 18e61fb 
  
ambari-server/src/main/resources/common-services/HDFS/2.1.0.2.0/package/scripts/hdfs_namenode.py
 635f159 
  ambari-server/src/test/python/stacks/2.0.6/HDFS/test_namenode.py 4a89b0a 

Diff: https://reviews.apache.org/r/48708/diff/


Testing
-------

PENDING


Thanks,

Jonathan Hurley

Reply via email to