Results 1 to 2 of 2

Thread: 404 on first request to liverepeater-edge with failing first OriginURL

  1. #1
    Join Date
    Oct 2013
    Posts
    4

    Default 404 on first request to liverepeater-edge with failing first OriginURL

    Hi all,

    I have two liverepeater-edge applications talking to two liverepeater-origin applications (which are doing the HLS packetizing).

    The Repeater configuration is as follows:

    <Repeater>
    <OriginURL>wowz://10.128.18.133/origin|wowz://10.128.18.165/origin</OriginURL>
    ...

    For simplicity, I'll refer to these servers 133 and 165. :-)

    If I have a working stream pushing to 133's liverepeater-origin, a request to 133's liverepeater-edge immediately returns a 200.

    If there is a working stream pushing to 165 but *not* to 133, then a request to 133's liverepeater-edge takes a while to return a 404, then I can see in its logs that it's failing over to using 165 as the origin, after which subsequent requests to 133's liverepeater-edge immediately return a 200.

    It boils down to this: The liverepeater-edge has to discover that its OriginURL is failing before trying the other, and it only does so AFTER the first request.


    Is there a way to work around this, or is it something I should raise as a bug?

    Thanks!
    Jeff

  2. #2
    Join Date
    May 2013
    Posts
    680

    Default

    One option would be to utilize our IMediaStreamNameAliasProvider2 to dynamically resolve the origin. This way you could do your own health checks on each origin before determining which to resolve.

Similar Threads

  1. Replies: 1
    Last Post: 06-01-2014, 03:16 AM
  2. Replies: 11
    Last Post: 08-21-2013, 07:36 AM
  3. Dynamic OriginURL in liverepeater/edge
    By robw21 in forum General Forum
    Replies: 3
    Last Post: 06-11-2013, 07:05 PM
  4. Replies: 3
    Last Post: 02-01-2013, 12:36 PM

Posting Permissions

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