Please note you should add the following parameter to flashphoner.properties file of Edge instance4. Create HTTP legacy health check. Note that load balancer always checks server root “/”
With this setting we got unhealth instance.
We are forced to change from "/" to "/health-check" and then we got a green flag as health instance on load balance.
The manual is common and describes WebRTC Edges only. You can add any necessary ports to the load balancer.5. Create frontend configuration for HTTP(S) WCS ports and WS(S) WSC ports. Select “Create static IP” and create static IP address for load balancer
Missing port 8445 for HLS stream
Java 8 is good enough for development but may be not so stable under high load. That's why we recommend to use JDK 12 or 14 and ZGC for high loaded servers.a-) Why using Java 12 and not 1.8 as default?
We've tested it by publishing WebRTC stream with certain resolution (HD or FullHD if channel bandwidth allows) and playing it with another one, this will enable transcoding on edge server and will load CPU over 80% depending on encoders quantity.b-) How can I simulate load to reach 80% of CPU to check if new servers are going up and running?
Sorry, we missed this moment in doc. You should set up SSL right after creation of Origin and Edge instances:I followed the document and deployed the setup. I am not sure how to set up SSL on the edge as domain is linked with the external IP of the load balancer. I have normally used the cert-auto tool and certified the domain using letsencrypt, download the pem files, and upload them using the admin.
This is the load balancer issue. It uses Client IP and protocol to bind requests from one client to one server. So you have to test from two different IPs to make sure requests go to a new instance.The second question is, I used the console application and generated the load, after 80% cpu a new instance was created but no traffic was going to it.
The default media ports range (31001-32000) allows no more than 400 WebRTC connections. So you have to expand this range, update project firewall rules and Edge disk image.
Unfortunately, no. There is a three main types of Load balancers in Google Cloud Platform:Would you not just install the SSL on the load balancer as the domain will be linked with LB IP
You're right.1 - create a node edge with SSL like edge.yourdomain.com
2 - install it on WCS as described
3 - point LOAD BALANCE IP to like edge.yourdomain.com
4 - no matter how many edges do you start, all of them has the same domain name and SSL and also the same image from WCS settings.
This is known autoscaling issue, it can be reproduced in AWS LB with autoscaling too.An instance has been "shutdown" from LB but users were connected to them.