Difference between revisions of "Building Helix Server Cluster using LVS"

Revision as of 05:57, 8 April 2007

Introduction

Helix is an open source project started by Real Networks to provide audio and media service.

A single Helix always has its limitation in performance. Server cluster can be used to scale up the performance of the whole Helix media system.

Helix streaming service uses the following protocols:

• PNM (TCP on port 7070, UDP from server -> player on ports 6970-7170)
• RTSP (TCP on port 554, similar UDP as above, but often on multiple ports)
• PNM was our original, but now mostly legacy, protocol used in our versions 1 through 5.
• There's also a HTTP/TCP-only fallback mode which is (usually) on port 8080.

Architecture

Configuration Example

VS/NAT

Run the follwing script on LB Server:

ipvsadm -A -t 192.168.9.244:554  -s rr
ipvsadm -a -t 192.168.9.244:554  -r 192.168.0.150 -m
ipvsadm -a -t 192.168.9.244:554  -r 192.168.0.160 -m

Run

realplay rtsp://192.168.9.244/test.rm

for a test.

VS/DR

Run the follwing script on LB Server:

ipvsadm -C
ipvsadm -A -t 192.168.9.200:554  -s rr
ipvsadm -a -t 192.168.9.200:554  -r 192.168.9.150 -g
ipvsadm -a -t 192.168.9.200:554  -r 192.168.9.160 -g

Run

realplay rtsp://192.168.9.200/test.rm

for a test.

Conclusion

References

• How Do You Scale Your Digital Media Deployment
• http://archive.linuxvirtualserver.org/html/lvs-users/2001-06/msg00097.html

"Building Helix Server Cluster using LVS" is an LVS Example related stub. You can help LVSKB by expanding it