Uploaded image for project: 'Hive'
  1. Hive
  2. HIVE-16061

When hive.async.log.enabled is set to true, some output is not printed to the beeline console

Log workAgile BoardRank to TopRank to BottomBulk Copy AttachmentsBulk Move AttachmentsVotersWatch issueWatchersCreate sub-taskMoveLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 2.1.1
    • 3.0.0
    • Logging
    • None

    Description

      Run a hiveserver2 instance "hive --service hiveserver2".
      Then from another console, connect to hiveserver2 "beeline -u "jdbc:hive2://localhost:10000"

      When you run a MR job like "select t1.key from src t1 join src t2 on t1.key=t2.key", some of the console logs like MR job info are not printed to the console while it just print to the hiveserver2 console.

      When hive.async.log.enabled is set to false and restarts the HiveServer2, then the output will be printed to the beeline console.

      OperationLog implementation uses the ThreadLocal variable to store associated the log file. When the hive.async.log.enabled is set to true, the logs will be processed by a ThreadPool and the actual threads from the pool which prints the message won't be able to access the log file stored in the original thread.

      Attachments

        1. HIVE-16061.1.patch
          16 kB
          Aihua Xu
        2. HIVE-16061.2.patch
          2 kB
          Aihua Xu
        3. HIVE-16061.3.patch
          47 kB
          Aihua Xu
        4. HIVE-16061.4.patch
          93 kB
          Aihua Xu

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            aihuaxu Aihua Xu Assign to me
            aihuaxu Aihua Xu
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment