Uploaded image for project: 'UIMA'
  1. UIMA
  2. UIMA-3657

DUCC Orchestrator (OR) improved synchronization tracking

VotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 1.0.0-Ducc
    • 1.1.0-Ducc
    • DUCC
    • None

    Description

      The orchestrator currently records to its log some limited and incomplete information about synchronization. This improvement:

      1. Instruments all WorkMap synchronizations in the OR
      2. Accounts for time blocked and time held
      3. Records all new requests for synchronization when current holder exceeds 10 seconds
      4. Records all pending requests when current holder releases having held synchronization for > 10 seconds

      This is to address the situation, for example, where OR is running albeit slowly. Newly added log messages will hopefully shed light on where the bottlenecks may be.

      One theory is that a normally fast resource, such as the filesystem, becomes very slow and bogs down OR while its trying to write its checkpoint dataset. In this case, we'd expect to see the synchronization lock held for a long time by the OR's checkpoint module.

      Attachments

        Activity

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

          People

            lou.degenaro Lou DeGenaro
            lou.degenaro Lou DeGenaro
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment