Results 1 to 7 of 7

Thread: Disconnecting the current session between a live repeater edge and the origin

  1. #1

    Default Disconnecting the current session between a live repeater edge and the origin


    We have a set of live repeater origin servers that are behind a load balancer. The edge servers use a custom API to identify the active origin for a feed. What we're noticed is that once an edge establishes a session with an origin, that session is kept active until the last client disconnects from the edge. As a result, when the origin server for a particular feed changes, the edge fails to connect to it instead. How do we kill the active session to the old origin? Configuring the edge with multiple origin servers is not a valid option in our case since we have a significant number of origin servers across the globe.


  2. #2



  3. #3
    Join Date
    Dec 2007


    You don't have to configure the server for multiple origins if you use .stream files to point to the origin, in which case you can just change the contents of the .stream file on the edge. When the first client connects to that edge stream, the edge should initiate a connection to the new origin.


  4. #4


    The origin for a feed can change at any time, with varying levels of frequency. Triggering an update to the .stream file across all our wowza edges will not be feasible. The .stream file approach was suggested earlier and due to the scaling issue, we decided to use the StreamNameAlias module to set the origin dynamically.

    So is there no way to kill the connection to the old origin?

  5. #5
    Join Date
    Dec 2007


    I think you will have to kill all the playback clients that are connected to the edge which is sourcing the origin you want to disconnect from. You an disconnect on the origin side, but I think the MediaCaster system on the edge will reconnect in a few seconds. For RTMP clients:

    List<IClient> clients = appInstance.getClients();
    Iterator<IClient> iter = clients.iterator();
    	IClient client =;
    	if (!client.isConnected())

  6. #6


    Is there an API that can be used by the edge to disconnect itself from the origin? The way, the origins don't have to keep track of what feeds are assigned to them vs others.
    Last edited by vjagannathan; 11-12-2013 at 02:35 PM.

  7. #7


    I believe I know how to do that already. Will give it a shot. Thanks.

Similar Threads

  1. HLS Live Streaming origin-edge repeater
    By PaltopVince in forum Live Streaming and Encoders
    Replies: 4
    Last Post: 09-02-2016, 09:43 AM
  2. Live Repeater Origin-Edge and HTTP Caching Origin
    By vjagannathan in forum General Forum
    Replies: 3
    Last Post: 06-18-2014, 02:56 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts