All Products
Search

This Product

    E-MapReduce:What do I do if a JournalNode error occurs?

    Document Center

    E-MapReduce:What do I do if a JournalNode error occurs?

    Last Updated:Mar 26, 2026

    This topic describes the cause and fix for a JournalNode error in EMR on ECS.

    Error message

    The following error appears in JournalNode logs:

    org.apache.hadoop.hdfs.server.namenode.FSImage: Caught exception after scanning through 0 ops from /current/edits_inprogress_0000000000000191004 while determining its valid length. Position was 1036288 java.io.IOException: Can't scan a pre-transactional edit log.

    Cause

    In most cases, this error means the edits file was corrupted due to power loss or disk space running out while data was being written to the JournalNode.

    Solution

    The recovery path depends on whether the associated NameNode is healthy. Check the NameNode status first.

    If the NameNode is running normally, restore the JournalNode by completing these steps in order:

    1. Perform a checkpoint on the NameNode to flush the current edit log to disk.

    2. Fix the abnormal JournalNode component on the node to restore the JournalNode independently.

    3. View the Journal Status on the HDFS web UI to confirm the fix.

    If the NameNode fails to start, see What do I do if a NameNode fails to start due to an EditsLog error on a JournalNode?.