Uploaded image for project: 'Hadoop HDFS'
  1. Hadoop HDFS
  2. HDFS-13544

Improve logging for JournalNode in federated cluster

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 2.10.0, 3.2.0, 3.1.1, 3.0.3
    • federation, hdfs
    • None
    • Reviewed

    Description

      In a federated cluster,when two namespaces utilize the same JournalSet, it is difficult to decode some of the log statements as to which Namespace it is logging for.
      For example, the following two log statements do not tell us which Namespace the edit log belongs to.

      INFO  server.Journal (Journal.java:prepareRecovery(773)) - Prepared recovery for segment 1: segmentState { startTxId: 1 endTxId: 10 isInProgress: true } lastWriterEpoch: 1 lastCommittedTxId: 10
      
      INFO  server.Journal (Journal.java:acceptRecovery(826)) - Synchronizing log startTxId: 1 endTxId: 11 isInProgress: true: old segment startTxId: 1 endTxId: 10 isInProgress: true is not the right length

      We should add the NameserviceID or the JournalID to appropriate JournalNode logs to help with debugging.

       

      Attachments

        1. HDFS-13544.001.patch
          19 kB
          Hanisha Koneru

        Activity

          People

            hanishakoneru Hanisha Koneru
            hanishakoneru Hanisha Koneru
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: