Uploaded image for project: 'Solr'
  1. Solr
  2. SOLR-17203

CPU not calculated correctly in ThreadCpuTimer

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

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • main (10.0), 9.6
    • main (10.0), 9.6
    • Query Limits
    • None

    Description

      Naming is hard, and the initial implementation seems to have stumbled on a method naming confusion with the effect that it was only possible to hit a cpu time out shortly after a new thread is created (which is true when the tests run, and thus the test was passing). Essentially it was grabbing an elapsed time for the timer and, treating it as the total time for the thread.

      Fixed locally, will submit PR soon...

      Attachments

        Activity

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

          People

            gus Gus Heck
            gus Gus Heck
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0h
                0h
                Logged:
                Time Spent - 1h 40m
                1h 40m

                Slack

                  Issue deployment