Uploaded image for project: 'Grouper'
  1. Grouper
  2. GRP-5083

Loader Failsafes: Information Improvements

    XMLWordPrintable

Details

    • Improvement
    • Resolution: Unresolved
    • Minor
    • None
    • 4.5.5
    • grouperLoader
    • None

    Description

      We had a sql-list loader job trigger a failsafe and found a few ways that would help us handle it.

      1. I was hoping, at least, the Loader Job message box would have a description of what the failsafe trigger was (too many fewer groups, groups that were going to shrink to much) along with the numbers
      2. Instead, we had to do a subjob search and scroll through thousands of subjobs and luckily only one group had a failsafe trigger. Luckily the Loader Job did not exceed 4k groups, otherwise we wouldn't have been able to find the information in the UI
        1. It would have helped if subjob+error-only filter would have just shown the relevant groups
        2. Once the right group/subjob was found, the Loader Message field had terrific information about shrinkage and original size. It might help to put some (3-10) example subjects into the message to help sanity check the failsafe
      3. The 'Approve Failsafe' job action was in a great location in the Daemon Log pulldown, but we were hoping it would bring up a page explaining the Failsafe situation, and, ideally, offering some selective approvals. Instead, it seemed to blindly approve whatever failsafes were outstanding.

      Attachments

        Activity

          People

            chris.hyzer@at.internet2.edu Chris Hyzer (upenn.edu)
            bert.beelindgren@at.internet2.edu Bert Bee-Lindgren (gatech.edu)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: