Uploaded image for project: 'IMPALA'
  1. IMPALA
  2. IMPALA-4566

Kudu client glog contention can cause timeouts

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Critical
    • Resolution: Fixed
    • Impala 2.8.0
    • Impala 2.8.0
    • Backend

    Description

      There appears to be significant contention in glog from the Kudu client threads under stressful workloads, we believe resulting in timeouts/failed queries.

      Kudu JIRA: https://issues.apache.org/jira/browse/KUDU-695

      Todd filed a glog upstream JIRA to address the contention. The Kudu client may need to be more careful with what is getting logged.

      In Impala, we can mitigate some of this by setting the Kudu log level separately from the Impala log level, and offering the ability to disable the Kudu client logging completely.

      Attachments

        Activity

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

          People

            mjacobs Matthew Jacobs
            mjacobs Matthew Jacobs
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment