Results 1 to 5 of 5

Thread: EC2 instances using the same server id in load balancing?

  1. #1

    Default EC2 instances using the same server id in load balancing?

    I recently was brought in to add capacity to an existing cluster of Wowza servers via Amazon EC2.

    Due to project requirements, I needed to run the servers on a custom Ubuntu build, so I can't use the default images for Wowza provided. I also needed to use Elastic Block Store as opposed to instance storage, which the current Wowza AMI images use. Thus, I built my custom AMI on a stock Ubuntu server install provided by the Ubuntu team. I got a daily license, and installed it by default in my template AMI, and tested it to make sure things were working alright. I then went on to create about 20 images needed for the broadcast tonight.

    After creating two instances, I noticed that something weird was happening: only one of them was showing up in the "loadbalancer?showServerXML" view! Then, I realized what was happening: both EC2 instances have the same "serverId" and thus after refreshing repeatedly, I'd see things alternate between my two servers. Basically, this means that a hundred servers can show up as 1 server to the load balancer, as they seem to have the same server id.

    Is there a workaround for this? For now, my load-balancing for my EC2 instances seems to basically be a round-robin approach, where every time it's luck of the draw, rather than being properly balanced. It works, but not well. If two servers ping really close together, there's a good chance that one of them will never get any load.

    Is this a known bug? Is there something I can do to mitigate this?

  2. #2

    Default

    If you created your own AMI based on our AMI then this can happen. You need to either rebulid your AMI after deleting the file:

    /usr/local/WowzaMediaServer/conf/Server.guid

    Or you need to delete this file when an AMI is started before Wowza Server starts. When Wowza Server starts and this file is not present a new guid will be created for the server.

    Charlie

  3. #3

    Default

    So a simple "rm $WOWZA_HOME/conf/Server.guid" will fix all of my problems if I put it in, say, $WOWZA_HOME/bin/startup.sh, $WOWZA_HOME/bin/wms.sh, or /etc/init.d/WowzaMediaServer?

  4. #4

    Default

    Yes, that is correct.

    Charlie

  5. #5

    Default

    Awesome, thanks

Similar Threads

  1. Replies: 1
    Last Post: 05-02-2012, 07:18 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
  •