Uploaded image for project: 'Sakai'
  1. Sakai
  2. SAK-40709

SiteStats aggregator job running multiple times on same events

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: CLOSED
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 11.4
    • Fix Version/s: None
    • Component/s: Sitestats
    • Labels:
      None
    • Environment:
      Oracle
    • Test Plan:
      Hide

      Please add a Test Plan here.

      Show
      Please add a Test Plan here.

      Description

      In testing SiteStats for use at our institution, I disabled real-time event aggregation and ran the StatsAggregateJob on all the events in the database. During these tests, often the job would run on the same data for multiple executions in a row.

      I traced it to the fact that the the id inserted into SST_JOB_RUN table was smaller than existing entries.  That causes the incorrect behavior because the job orders the results by ID to determine the sakai_event id to start from on the next run.

        Gliffy Diagrams

          Zeplin

            Attachments

              Activity

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  curtisvo Curtis van Osch
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Git Integration