We use cookies to enhance your browsing experience, serve personalized ads or content, and analyze our traffic. By clicking "Accept All", you consent to our use of cookies. Click here for more information on our Privacy Policy.
Customize Consent Preferences
We use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below.
The cookies that are categorized as "Necessary" are stored on your browser as they are essential for enabling the basic functionalities of the site. ...
Always Active
Necessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data.
No cookies to display.
Functional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features.
No cookies to display.
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc.
No cookies to display.
Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.
No cookies to display.
Advertisement cookies are used to provide visitors with customized advertisements based on the pages you visited previously and to analyze the effectiveness of the ad campaigns.
Use the Event Scheduling API to schedule a scale-up of an existing nodegroup, or create a new nodegroup at a precise time. Use a tool like this date-to-millisecond-calculator to generate the date in miliseconds required. Note that this is universal timestamp, so it doesn’t matter what timezone you use to calculate the event time. The eventName value is for your records only, and should be descriptive of the event that you are scheduling (for example, big-event-saturday-night).
It is important to note that autoscaling startup times vary based on platform type and instance type. For example, instances on AWS usually take between 70 to 90 seconds whereas Azure VMs can take up to 140 seconds for startup. Startup time includes VM initialization and Red5 Pro service startup. Use this to estimate the total time needed for all your instances to be ready prior to scheduling. And finally make sure to add a buffer time for your cluster spinup.
Scheduling a new nodegroup to be created for a event will require you to initialize your cluster before the actual event time. The function to define the average cluster prepration time can be defined as:
(TOTAL NODES X AVERAGE STARTUP TIME PER NODE)+ SETUP BUFFER TIME
So if you require a minimum of 1 origin & 10 edges and your average startup time is assumed to be 120 seconds per node, then you should schedule the event using the Stream Manager Event Scheduler API for, (11 X 120)+100=1320 seconds (22 minutes) (where 100 is the additional total buffer time for you setup to account for unexpected delay in operations).
Very similarly when you plan to resize (scale-up) an existing nodegroup, you should know that it will take the autoscaling mechanism a minimum of (ADDITIONAL NODES TO SCALE-UP X AVERAGE STARTUP TIME PER NODE) seconds for the group to reach desired capacity.
NOTE: Currently this feature is only available for use with “simple” clusters (containing origin and edge nodes only).
To create and initialize a new nodegroup for an event, at a scheduled time, you must provide an existing launchConfig name (must exist), a new scalePolicy name (must not exist) as shown in the JSON data sample below.
To resize an existing nodegroup for an event at a scheduled time, you must specify the name of the target in the data JSON Object as shown in the sampe below. For an existing nodegroup, launchConfig and scalePolicy are not to be specified, as they were already defined in the initial setup of the nodegroup.
The content of data is arbitrary and will depend on the type of scheduling (create/resize) requested and input specified. A create response will contain launchConfig and scalePolicy attributes, whereas resize/update response will contain a nodeGroup attribute denoting the target nodegroup to be resized.
The content of data is arbitrary and will depend on the type of scheduling (create/resize) requested and input specified. A create response will contain launchConfig and scalePolicy attributes, whereas resize/update response will contain a nodeGroup attribute denoting the target nodegroup to be resized.