OriginCluster: Same stream may exist in two origin servers.

[jinleileiking]

Description'

Please ensure that the markdown structure is maintained.

1. SRS version: 4.0'

Please ensure that the markdown structure is maintained.

1. The configuration of SRS is as follows (Config):

Please ensure that the markdown structure is maintained.

To form a cluster with 2 origins and 2 edges, use statefulsets for the 2 origins and deployments for the 2 edges. Expose port 1935 for the edges using a load balancer.

Please ensure that the markdown structure is maintained.

Replay

Please ensure that the markdown structure is maintained.

Translation:

First, let's assume the path used is e1 -> o1.
If we try to push the same flow again, the path remains e1. However, since it reaches the same machine, it cannot be pushed up, which is expected.
Now, let's consider the path e2 -> o1. Since o1 cannot be pushed up, it also meets the expected outcome.
Continuing with persistent attempts, finally, there is one instance where the path used is e2 -> o2. Since o2 does not have to go to coworker o1 to find the flow, it can also be pushed up.

Please ensure that the markdown structure is maintained.

Translation:

Is this problem not being resolved because it involves central states? Or is it considered to be reasonable?

Please ensure that the markdown structure is maintained.

Translation:

The way to solve this problem is also very simple: just use on_publish to obtain the stream status from the central service.

Please ensure that the markdown structure is maintained.

Translation:

Alternatively, you can add o1 to o2... the logic of checking if the stream exists in other origin servers.

Please ensure that the markdown structure is maintained.

TRANS_BY_GPT3

[winlinvip]

Crazy push, finally there was a time when using e2 -> o2 because o2 did not reach coworker o1 to find the flow, so it also pushed up.

Why did o2 not reach o1 to find the flow? Is there a simple way to reproduce it?

TRANS_BY_GPT3