To improve application robustness, Agora recommends that you do the following when integrating Cloud Recording RESTful APIs:
If you send a Cloud Recording RESTful API request to
api.agora.io and the request fails, retry with the same domain name first. If it fails again, replace the domain name with
api.sd-rtn.com and retry. Agora recommends that you use a backoff strategy, for example, retry after 1, 3, and 6 seconds successively, to avoid exceeding the Queries Per Second (QPS) limits.
You can use Cloud Recording RESTful APIs to acquire the status of the recording service. Apart from Cloud Recording RESTful APIs, you can use the Message Notification Service as a complementary method to get the service status.
sid. Redundant message notification still cannot guarantee a 100% arrival rate.
Take the following steps to ensure that the recording service starts successfully:
Ensure that the
start request is successful, that is, you receive a
sid (recording ID) from the response. If the request fails, take measures according to the HTTP status code:
40x, check the parameter values in your request.
50x, you can retry several times with the same parameters until you receive a
sid. Agora recommends that you use a backoff strategy, for example, retry after 3, 6, and 9 seconds successively, to avoid exceeding the QPS limits. If you retry three times and still do not get a
sid, retry with a new user ID.
65, retry with the same parameters. Agora recommends that you use a backoff strategy, for example, retry after 3 and 6 seconds successively.
Five seconds after you receive a
sid, use a backoff strategy to call
query. Agora recommends that the interval between two
query calls is shorter than
maxIdleTime, which you set in the
start call. If the
query call succeeds, and
5, it means the recording service starts successfully. Otherwise, you can deem the recording service as not having started, or quit halfway after starting.
You can periodically call
query to ensure that the recording service is in progress and in a normal state. Apart from
query, you can use the Message Notification Service as a complementary method to monitor the service status. See Comparison Between the Message Notification Service and the
query Method for detailed comparison between the two methods.
If the reliability of the status of a cloud recording is a high priority, Agora strongly recommends using the
query method to periodically query the recording service status. The interval between two calls can be around two minutes. Take the corresponding measure based on the received HTTP status code:
40x, check the parameter values in your request.
404, and the request parameters are confirmed to be correct, the recording has either not started successfully, or the recording quit after starting. Agora recommends that you use a backoff strategy, for example, retry after 5, 10, and 15 seconds successively.
queryrequest failed, but it is not clear whether the recording has quit. The
50xerror is rare. You can continue to use the backoff strategy (waiting for 5 seconds, 10 seconds, 15 seconds, or 30 seconds) to call
After enabling the redundant message notification function, you need to deduplicate messages based on
sid. For example, if you need to start recording again after a recording session times out and quits, the process is:
11, which means that the recording service quits normally.
acquireto restart the recording service.
sidcontained in the above notifications is identical to the previous ones, you can ignore them as redundant notifications.
queryif you need to fully ensure that the recording service successfully starts.
You can obtain the M3U8 file name by two means. One is by splicing according to the file naming rules. The other is by calling the
query method. Agora recommends that you use splicing to obtain the M3U8 file name.
In composite recording mode, the format of the M3U8 file name is
<sid>_<cname>.m3u8. Therefore, you can predict the M3U8 file name by splicing. See Naming conventions for details.
The M3U8 file name is generated after the first slice file is generated. Therefore, you should call
query after the first slicing completes. See Slicing for details.
In composite recording mode, call
query 15 seconds after the cloud recording starts; in individual recording mode, call
query one minute after the cloud recording starts. If the first
query call fails, you can try again after one minute.
The default value of
maxIdleTime in the
start method is 30 seconds. If the host frequently goes online and offline, a brief
maxIdleTime value causes the recording service to join and exit the channel frequently. For scenarios that require the recording service to be in the channel all the time, it is necessary to increase
maxIdleTime in case the recording quits after a short idle time.
For example, if there is a fixed 5-minute break in each class, you can set
maxIdleTime to 10 minutes to ensure uninterrupted recording of the entire class.