Uploaded image for project: 'NetarchiveSuite'
  1. NetarchiveSuite
  2. NAS-1926

The HarvestDispatcher info log is not very informative

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Minor
    • 3.17.0, I48
    • 3.16.1
    • Harvest Definition
    • None
    • SB/KB
    • Hide

      1. Start a NAS system.
      2. Verify that the log contains information about the addition of harvesters.
      3. Run through a selective harvest and verify that the log contains entries on: The removal of an Available Harvester and the later addition of the harvester as Available Harvester.

      Show
      1. Start a NAS system. 2. Verify that the log contains information about the addition of harvesters. 3. Run through a selective harvest and verify that the log contains entries on: The removal of an Available Harvester and the later addition of the harvester as Available Harvester.

    Description

      We currently have a log looking like:

      HIGHPRIORITY: [high_8082, high_8084, high_8085, high_8086]
Aug 17, 2011 8:32:58 AM dk.netarkivet.harvester.scheduler.HarvestDispatcher$DispatchState updateHarvesterStatus
INFO: Available harvesters:
LOWPRIORITY: [low_8081, low_8082, low_8083, low_8087, low_8088]
HIGHPRIORITY: [high_8082, high_8084, high_8086]
Aug 17, 2011 8:32:58 AM dk.netarkivet.harvester.scheduler.HarvestDispatcher$DispatchState updateHarvesterStatus
INFO: Available harvesters:
LOWPRIORITY: [low_8081, low_8082, low_8083, low_8087, low_8088]
HIGHPRIORITY: [high_8082, high_8084, high_8085, high_8086]
Aug 17, 2011 8:32:58 AM dk.netarkivet.harvester.scheduler.HarvestDispatcher$DispatchState updateHarvesterStatus
INFO: Available harvesters:
LOWPRIORITY: [low_8081, low_8082, low_8083, low_8087, low_8088]
HIGHPRIORITY: [high_8082, high_8084, high_8085]
Aug 17, 2011 8:32:58 AM dk.netarkivet.harvester.scheduler.HarvestDispatcher$DispatchState updateHarvesterStatus
INFO: Available harvesters:
LOWPRIORITY: [low_8081, low_8082, low_8083, low_8087, low_8088]
HIGHPRIORITY: [high_8082, high_8083, high_8084, high_8085]
Aug 17, 2011 8:32:58 AM dk.netarkivet.harvester.scheduler.HarvestDispatcher$DispatchState updateHarvesterStatus
INFO: Available harvesters:
LOWPRIORITY: [low_8081, low_8082, low_8083, low_8087, low_8088]
HIGHPRIORITY: [high_8082, high_8083, high_8084, high_8085, high_8086]
Aug 17, 2011 8:32:59 AM dk.netarkivet.harvester.scheduler.HarvestDispatcher$DispatchState updateHarvesterStatus
INFO: Available harvesters:
LOWPRIORITY: [low_8081, low_8082, low_8083, low_8087, low_8088]
HIGHPRIORITY: [high_8082, high_8083, high_8084, high_8085]
Aug 17, 2011 8:32:59 AM dk.netarkivet.harvester.scheduler.HarvestDispatcher$DispatchState updateHarvesterStatus
INFO: Available harvesters:
LOWPRIORITY: [low_8081, low_8082, low_8083, low_8087, low_8088]
HIGHPRIORITY: [high_8082, high_8083, high_8084, high_8085, high_8086]
Aug 17, 2011 8:32:59 AM dk.netarkivet.harvester.scheduler.HarvestDispatcher$DispatchState updateHarvesterStatus

      Here a lot of 'Available Harvester' state is logged, but no information on what is cause the apparent state changes. As the cause for the state change is at least as importent as the state itself this should be logged.

      This include:

      • The HarvestStatusMessage causing the change.
      • The HarvestJob dispatching.

      Attachments

        Activity

          People

            mss Mikis Seth Sørensen (Inactive)
            mss Mikis Seth Sørensen (Inactive)
            Søren Vejrup Carlsen Søren Vejrup Carlsen (Inactive)
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

                Estimated:
                Original Estimate - 2h
                2h
                Remaining:
                Remaining Estimate - 0h
                0h
                Logged:
                Time Spent - 2h
                2h