This looks like a case of edit logs getting reordered. As
@bgooley noted, it is similar to HDFS-12369, where the OP_CLOSE is appearing after OP_DELETE causing the file to be absent when replaying the edits.
The simplest fix, depending on if this is the only file instance of the reordered issue in your edit logs, would be to run the NameNode manually in an edits-recovery mode and "skip" this edit when it catches the error. The rest of the edits should apply normally and let you start up your NameNode.
The recovery mode of NameNode is detailed at
https://blog.cloudera.com/blog/2012/05/namenode-recovery-tools-for-the-hadoop-distributed-file-system/If you're using CM, you'll need to use the NameNode's most recent generated configuration directory under /var/run/cloudera-scm-agent/process/ on the NameNode host as the HADOOP_CONF_DIR, while logged in as 'hdfs' user, before invoking the manual NameNode startup command.
Once you've followed the prompts and the NameNode appears to start up, quit out/kill it to restart from Cloudera Manager normally.
If you have a Support subscription, I'd recommend filing a case for this, as the process could get more involved depending on how widespread this issue is.
