Uploaded image for project: 'Moodle'
  1. Moodle
  2. MDL-75531

The BigBlueButton server should be polled at regular interval via cron

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • 4.0.2, 4.0.5, 4.1, 4.4
    • BigBlueButton
    • MOODLE_400_STABLE, MOODLE_401_STABLE, MOODLE_404_STABLE
    • MDL-75531-master
    • Hide

      Note this ticket depends on MDL-77186, so it should only be integrated after MDL-77186 is merged.

      1. # Create a new BBB Meeting B1
      2. Run the cron through cli (it should now be kept alive for 3 minutes by default, see MDL-77186)
      3. Join a meeting
      4. Check that the adhoc task refreshes the cache (for now it will take a 5 seconds to be updated) and the information is updated
      5. End the meeting
      6. Check that the meeting information is updated

       

      Show
      Note this ticket depends on MDL-77186 , so it should only be integrated after MDL-77186 is merged. # Create a new BBB Meeting B1 Run the cron through cli (it should now be kept alive for 3 minutes by default, see MDL-77186 ) Join a meeting Check that the adhoc task refreshes the cache (for now it will take a 5 seconds to be updated) and the information is updated End the meeting Check that the meeting information is updated  

      The ``retrieve_cached_meeting_info method``` of the meeting instance caches the current data for a meeting.
      This is prevents Moodle from querying the Bigbluebutton server every time a student want to know the meeting's status.
      However, if we disconnect the Bigbluebutton server AND the cache expires, then each student query will also try to retrieve the information on the BigblueButton server.
      If the BBB server is slow to answer this might lead to a lot of queries being left pending on the Moodle side, which means that it will load the Moodle server unnecessarily.

      The aim of this ticket is:

      • To make sure that when we fetch info from the BBB server and either there is an error (we detect the server is down) or the query times
        out, the we prevent other queries from being sent, at least for some time.
      • We display an error status on each BBB meeting so the user is aware that there is an issue on the server.

        1. Meeting refresh (1).jpg
          Meeting refresh (1).jpg
          66 kB

            Unassigned Unassigned
            lmdavid Laurent DAVID
            Shamiso Jaravaza Shamiso Jaravaza
            Votes:
            3 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:

                Estimated:
                Original Estimate - 0 minutes
                0m
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 1 hour
                1h

                  Error rendering 'clockify-timesheets-time-tracking-reports:timer-sidebar'. Please contact your Jira administrators.