Details

    • Type: Sub-task
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.0.2
    • Component/s: Operability
    • Labels:
      None
    • Release Note:
      Hide
      Log Master WAL Proc at INFO level so can tell where we transition; will help debugging/figuring accounting. Also change DEFAULT_RIT_CHORE_INTERVAL_MSEC from 5 to 60 seconds; makes it so we emit STUCK RIT notice once a minute only rather than 12 times a minute (latter was causing us to quickly roll-away the logging around problem 'events').
      Show
      Log Master WAL Proc at INFO level so can tell where we transition; will help debugging/figuring accounting. Also change DEFAULT_RIT_CHORE_INTERVAL_MSEC from 5 to 60 seconds; makes it so we emit STUCK RIT notice once a minute only rather than 12 times a minute (latter was causing us to quickly roll-away the logging around problem 'events').

      Description

      Emit when we roll master proc WAL so can see when they happen. Want to correlate instances of corruption w/ events on Master. Currently hard to do on a server where log-level is INFO (default for many deploys).

      Also, we log STUCK regions every 5 seconds. If a bundle of regions get stuck, we can log so frequently, we roll away where the problem happened so lose the chance to debug. Let me fix that too....

      Need both debugging instances of parent issue.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                stack stack
                Reporter:
                stack stack
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: