Uploaded image for project: 'Jackrabbit Oak'
  1. Jackrabbit Oak
  2. OAK-5059

DocumentCachingDataStoreStatsTest sometimes stuck

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

Details

    • Test
    • Status: Closed
    • Minor
    • Resolution: Fixed
    • None
    • 1.5.13, 1.6.0
    • it
    • None

    Description

      The test sometimes gets stuck when it starts on an existing MongoDB with data that was written with a Virtual clock. The log then writes a WARN message like this:

      14:01:57.823 WARN [main] DocumentNodeStore.java:2136 Detected clock differences. Local time is 'Thu Nov 03 14:01:57 CET 2016', while most recent external time is 'Thu Nov 03 15:00:00 CET 2016'. Current _lastRev entries: [r1582a7d3d6b-0-1]
      14:01:57.826 WARN [main] DocumentNodeStore.java:2143 Background read will be delayed by 3482,8 seconds. Please check system time on cluster nodes.
      

      Attachments

        1. unit-tests.log
          7.24 MB
          Julian Reschke
        2. unit-tests.log
          1.07 MB
          Julian Reschke

        Issue Links

        Activity

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

          People

            mreutegg Marcel Reutegger
            mreutegg Marcel Reutegger
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment