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

Job scheduler migration job is not available in Sakai 12

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Verified
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: 12.0, 19.0
    • Fix Version/s: 12.1, 19.0
    • Component/s: Quartz Scheduler
    • Labels:
      None
    • 12 status:
      Resolved
    • Test Plan:
      Hide
      • Login as Admin
      • Go to Job Scheduler
      • Click Jobs, New Job
      • You should see the job: "Scheduler: Migrate . . . " in the list
      • Give it a name and post it
      • Click Jobs
      • Click Triggers next to this job
      • Click "Run Job Now"

      Let it run, it should convert. Previously this job didn't even appear. In a empty database nothing will happen. I used the following values as test data to convert. After the script runs, this table (SCHEDULER_DELAYED_INVOCATION) will be empty and migrated to the quartz tables (like QRTZ_TRIGGERS)

      INSERT INTO `SCHEDULER_DELAYED_INVOCATION` VALUES ('02c57266-195e-4e50-bb47-72a8674fc8a6','2020-05-17 16:35:00','org.sakaiproject.content.providers.BaseEventDelayHandler','2'),('608ced0b-9b6c-4074-a274-8561520ad796','2020-05-10 16:35:00','org.sakaiproject.content.providers.BaseEventDelayHandler','1');
      

      Also if you check the logs there should be some text about migrations. (If they happened, or at minimal that the job ran)

      Show
      Login as Admin Go to Job Scheduler Click Jobs, New Job You should see the job: "Scheduler: Migrate . . . " in the list Give it a name and post it Click Jobs Click Triggers next to this job Click "Run Job Now" Let it run, it should convert. Previously this job didn't even appear. In a empty database nothing will happen. I used the following values as test data to convert. After the script runs, this table (SCHEDULER_DELAYED_INVOCATION) will be empty and migrated to the quartz tables (like QRTZ_TRIGGERS) INSERT INTO `SCHEDULER_DELAYED_INVOCATION` VALUES ('02c57266-195e-4e50-bb47-72a8674fc8a6','2020-05-17 16:35:00','org.sakaiproject.content.providers.BaseEventDelayHandler','2'),('608ced0b-9b6c-4074-a274-8561520ad796','2020-05-10 16:35:00','org.sakaiproject.content.providers.BaseEventDelayHandler','1'); Also if you check the logs there should be some text about migrations. (If they happened, or at minimal that the job ran)

      Description

      It seems like the migration job described in SAK-31819 was neither documented nor available as a job that can be selected.

      Therefore any delayed notifications created prior to the upgrade to Sakai 12 appear to be abandoned in the old scheduler_delayed_invocation table.

      We should have this available similar to the assignments job. I feel like the plan was below, however step 2 seems incomplete:

      1) Upgrade to 12
      2) Run the Scheduler Migration job (Assignment job has to run anyway so this isn't a big deal)
      3) Drop the scheduler_delayed_invocation table (and probably old assignment tables) in Sakai 13. . . Not sure since some schools may jump from 11 to 13 and skip 12, then we don't want to just drop them.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  jonespm Matthew Jones
                  Reporter:
                  jonespm Matthew Jones
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  5 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Git Source Code