Uploaded image for project: 'Blazegraph (by SYSTAP)'
  1. Blazegraph (by SYSTAP)
  2. BLZG-706

LOG BlockingBuffer not progressing at INFO or lower level

    Details

    • Type: New Feature
    • Status: Done
    • Resolution: Done
    • Affects Version/s: BIGDATA_RELEASE_1_2_2
    • Fix Version/s: None
    • Component/s: Bigdata SAIL

      Description

      Our logs get a lot of lines like:

      WARN  16:31:17.323 [main] c.b.r.accesspath.BlockingBuffer - Iterator is not progressing: ntries=275, elapsed=2004ms : BlockingIterator{ open=true, futureIsDone=false, bufferIsOpen=true, nextE=false}
      WARN  16:31:19.323 [main] c.b.r.accesspath.BlockingBuffer - Iterator is not progressing: ntries=411, elapsed=4003ms : BlockingIterator{ open=true, futureIsDone=false, bufferIsOpen=true, nextE=false}
      WARN  16:31:25.460 [main] c.b.r.accesspath.BlockingBuffer - Iterator is not progressing: ntries=281, elapsed=2000ms : BlockingIterator{ open=true, futureIsDone=false, bufferIsOpen=true, nextE=false}
      WARN  16:31:29.403 [main] c.b.r.accesspath.BlockingBuffer - Iterator is not progressing: ntries=278, elapsed=2005ms : BlockingIterator{ open=true, futureIsDone=false, bufferIsOpen=true, nextE=false}
      WARN  16:31:31.402 [main] c.b.r.accesspath.BlockingBuffer - Iterator is not progressing: ntries=365, elapsed=4004ms : BlockingIterator{ open=true, futureIsDone=false, bufferIsOpen=true, nextE=false}
      WARN  16:31:35.874 [main] c.b.r.accesspath.BlockingBuffer - Iterator is not progressing: ntries=275, elapsed=2009ms : BlockingIterator{ open=true, futureIsDone=false, bufferIsOpen=true, nextE=false}
      

      It seems that this is more a diagnostic message than a warning. Can the logging level be lowered to e.g. INFO? The code around it seems to suggest that INFO is actually the intended level, since the more computationally expensive code path for these messages is guarded with:

      if (log.isInfoEnabled() && !loggedStackTraces) {
      

      See BlockingBuffer line 1913-1939.

        Activity

        Hide
        bryanthompson bryanthompson added a comment -

        This information can be useful in tracking down mismatches in producer / consumer patterns. However, it is otherwise annoying. I have added a static final constant to BlockingBuffer that disables these code paths.

        Committed revision r6650.

        Show
        bryanthompson bryanthompson added a comment - This information can be useful in tracking down mismatches in producer / consumer patterns. However, it is otherwise annoying. I have added a static final constant to BlockingBuffer that disables these code paths. Committed revision r6650.

          People

          • Assignee:
            mikepersonick mikepersonick
            Reporter:
            gjdev gjdev
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: