apache/hadoop · error · IOException

No shared log found.

Error message

No shared log found.

What it means

Error "No shared log found." thrown in apache/hadoop.

Source

Thrown at hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSEditLog.java:1691

            + "too few journals successfully recovered.";
        LOG.error(msg, ex);
        synchronized (journalSetLock) {
          IOUtils.cleanupWithLogger(LOG, journalSet);
        }
        terminate(1, msg);
      } else {
        throw ex;
      }
    }
  }
  
  public long getSharedLogCTime() throws IOException {
    for (JournalAndStream jas : journalSet.getAllJournalStreams()) {
      if (jas.isShared()) {
        return jas.getManager().getJournalCTime();
      }
    }
    throw new IOException("No shared log found.");
  }
  
  public synchronized void doPreUpgradeOfSharedLog() throws IOException {
    for (JournalAndStream jas : journalSet.getAllJournalStreams()) {
      if (jas.isShared()) {
        jas.getManager().doPreUpgrade();
      }
    }
  }
  
  public synchronized void doUpgradeOfSharedLog() throws IOException {
    for (JournalAndStream jas : journalSet.getAllJournalStreams()) {
      if (jas.isShared()) {
        jas.getManager().doUpgrade(storage);
      }
    }
  }
  

View on GitHub (pinned to 2add963021)

Solutions

1. Configure a shared edits directory (dfs.namenode.shared.edits.dir, e.g. QJM) for HA setups.
2. Ensure the JournalNodes are running and reachable.

When it happens

Trigger: Log rolling or purge on shared (e.g. QJM) storage when no shared journal can be found among the configured journals.

Common situations: See trigger scenarios.

AI-assisted analysis of apache/hadoop@2add963021 (2026-08-22). Data as JSON: /api/errors/2f040e66a278005e. Report an issue: GitHub.