title: Hadoop Namenode Metadata - fsimage and edit logs
body: <p>I understand that the fsimage is loaded into the memory on startup and any further transactions are added to the edit log rather than to the fsimage for performance reasons.</p>
  
  <p>The fsimage in memory gets refreshed when the namenode is restarted. For efficiency, secondary name node periodically does a checkpoint to update the fsimage so that the namenode recovery is faster. All these are fine.</p>
  
  <p>But one point which i fail to understand is this,
  Lets say that a file already exists and the info about this file is in the fsimage in memory.
  Now i move this file to a different location, which is updated in the edit log.
  Now when i try to list the old file path, it complains thats it does not exists or whatever.</p>
  
  <p>Does this mean that namenode looks at the edit log as well which is contradictory to the purpose of the fsimage in memory? or how does it know that the file location has changed?</p>