/

Origin and Edge Nodes


Origin and Edge Nodes

In a simple nodegroup/cluster, the origin and edge roles are pretty straight forward:

  • Broadcasters are directed to the origin server(s)
  • Subscribers are directed to the edge server(s)

Example 1: Nodegroup created with one origin and one edge server.

  • origin server connectionCapacity set to 50. Alarm threshold set to 60% (default).
  • edge server connectionCapacity set to 400. Alarm threshold set to 60% (default).

Let's say this is a one-to-many scenario. So, one broadcaster/one stream.

When there are 241 subscribers, the stream manager will add a second edge server. New connections will be directed to whichever edge server has the least connections. To start, that will definitely be the new edge server, but some of the original subscribers might drop off, and at some point the traffic will be more evenly balanced between the two edge nodes. If at some point the second edge server reaches 241 connections, then a third edge server will be spun up, and so on until you reach the maxLimit defined in your scaling policy. When your subscribers drop off, or your broadcast ends, the nodegroup will scale back down, ultimately to the defined minLimit.

If the edge server reaches 400 connections, the defined connectionCapacity, the stream manager will no longer send any new connections to that server.

Note: edge servers will not be spun down if they have any active connections.