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

Option to send and retrieve events (via cluster mechanism) without going to the database

    XMLWordPrintable

    Details

    • Type: Feature Request
    • Status: CLOSED
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 2.8.x, 2.9.x, 10.0
    • Fix Version/s: 10.0
    • Component/s: Kernel
    • Labels:
    • 10 status:
      Resolved
    • Property addition/change required:
      Yes
    • Previous Issue Keys:
      KNL-1184

      Description

      The events processing in Sakai currently polls the sakai_events table periodically to check for new events on other nodes in the cluster that should be processed. This works OK for smaller installations (up to 4 nodes) but as the number of nodes in the cluster increases the number of requests against the events table goes up linearly. This becomes a serious load on the database as the number of events in the table increases and the number of nodes in the cluster increases (past 10 for example).

      There should be an optional way to send the events processing through a path which does not use the database so that events are only logged in the table but it is never polled by Sakai actively (except by stats processing - e.g. sitestats).

      Ideally, we would also remove some of the indexes from the events table at some point to reduce the load created by inserting events but this can happen later.

        Gliffy Diagrams

          Zeplin

            Attachments

            1. KNL-1184.patch.txt
              106 kB
            2. KNL-1184_trunk.patch
              33 kB
            3. KNL-1184_ets_remove.patch.txt
              0.6 kB
            4. KNL-1184_1.patch.txt
              17 kB

              Issue Links

                Activity

                  People

                  Assignee:
                  relong Bob Long
                  Reporter:
                  aaronz Aaron Zeckoski (Inactive)
                  Votes:
                  0 Vote for this issue
                  Watchers:
                  3 Start watching this issue

                    Dates

                    Created:
                    Updated:
                    Resolved:

                      Git Integration