XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Resolved
    • Trivial
    • Resolution: Fixed
    • None
    • None
    • hdfs-client
    • None

    Description

      Most of the public C++ FileHandle/FileSystem operations have a LOG_TRACE level message about parameters passed in etc. However many methods use LOG_DEBUG and a couple use LOG_INFO.

      We most likely want FS operations that happen a lot (read/open/seek/stat) to stick to LOG_DEBUG consistently and only use LOG_INFO for things like FileSystem::Connect or RpcConnection:: that don't get called often and are important enough to warrant showing up in the log. LOG_TRACE can be reserved for things happening deeper inside public methods and methods that aren't part of the public API.

      Related improvements that could be brought into this to avoid opening a ton of small Jiras:
      -Print the "this" pointer address in the log message to make it easier to correlate objects when there's concurrent work being done. This has been very helpful in the past but often got stripped out before patches went in. People just need be aware that operator new may eventually place an object of the same type at the same address sometime in the future.
      -For objects owned by other objects, but created on the fly, include a pointer back to the parent/creator object if that pointer is already being tracked (See the nested stucts in BlockReaderImpl).

      Attachments

        1. HDFS-10898.HDFS-8707.001.patch
          7 kB
          James Clampffer
        2. HDFS-10898.HDFS-8707.000.patch
          6 kB
          James Clampffer

        Activity

          People

            James C James Clampffer
            James C James Clampffer
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: