You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I have set up a source station cluster with three machines (1 master, 2 slaves), and several other machines as edges to pull streams from the source station, which is working fine. I am using the latest version of SRS 2.0. I have a few questions that I would like to ask everyone:
Although the source station cluster consists of three machines, only the master machine is receiving the push streams. This means that the push receiving capacity of the entire cluster is limited to the capabilities of the master machine, as a single SRS server has a maximum limit for pushing streams (e.g., 2k). In practice, how can this issue be resolved?
1.1 Even if the push stream access is done through Edge servers to distribute the load on different terminals, it will still ultimately converge on the Master server, which has the same limit of 2k for pushing streams. Is this understanding correct?
The Master and Slave servers form a simple hot backup system. When the Master server goes down, the Slave server also cannot receive the pushed streams (since the Slave's streams are forwarded by the Master). In this case, even if the Edge server is connected to the Slave, it cannot receive the RTMP streams. So, where does the hot backup function come into play in this scenario?
Continuing from the previous question, if the Edge server's origin is configured with the three mentioned source server IPs, will it automatically switch to the next one if one of the IPs goes down? What is the order of the switching? Is it round-robin or can it be configured?
If the Edge server's origin is configured with three source server IPs, namely master, slave1, and slave2, how does the Edge server determine which one is the master when receiving a live stream? If it selects a server that is not the master, such as slave2, how does the stream get forwarded to the master and slave1?
TRANS_BY_GPT3
The text was updated successfully, but these errors were encountered:
winlinvip
changed the title
关于Cluster:forward、edge、slave、master等的若干问题
About Cluster: Several questions about forward, edge, slave, master, etc.
Please maintain the markdown structure.
Jul 28, 2023
Hi,
I have set up a source station cluster with three machines (1 master, 2 slaves), and several other machines as edges to pull streams from the source station, which is working fine. I am using the latest version of SRS 2.0. I have a few questions that I would like to ask everyone:
1.1 Even if the push stream access is done through Edge servers to distribute the load on different terminals, it will still ultimately converge on the Master server, which has the same limit of 2k for pushing streams. Is this understanding correct?
The Master and Slave servers form a simple hot backup system. When the Master server goes down, the Slave server also cannot receive the pushed streams (since the Slave's streams are forwarded by the Master). In this case, even if the Edge server is connected to the Slave, it cannot receive the RTMP streams. So, where does the hot backup function come into play in this scenario?
Continuing from the previous question, if the Edge server's origin is configured with the three mentioned source server IPs, will it automatically switch to the next one if one of the IPs goes down? What is the order of the switching? Is it round-robin or can it be configured?
If the Edge server's origin is configured with three source server IPs, namely master, slave1, and slave2, how does the Edge server determine which one is the master when receiving a live stream? If it selects a server that is not the master, such as slave2, how does the stream get forwarded to the master and slave1?
TRANS_BY_GPT3
The text was updated successfully, but these errors were encountered: