<transcript><audio_52>those back-end servers can be running http ftp or ajp and ajp is what tomcat talks so you can use this as a front-end for any of those servers they don't have to be</transcript><transcript><audio_53>there's also a new module in 2-4 called mod heartbeat and mod heart monitor so heartbeat runs on the back end heart monitor runs on the front end and it ensures that servers are still alive if they aren't alive then they get</transcript><transcript><audio_54>and as i mentioned you can use mod proxy there's also a balancer manager which is a web-based front-end to the</transcript><transcript><audio_55>to the balancer so you can configure various settings on the balancer through that web interface and i realized right before my talk that i have a very old screenshot of this but if you can</transcript><transcript><audio_56>imagine it being exactly like this only it allows you to do neat things like add additional workers into the process if you bring up a new server on the back end you can add that in you can also</transcript><transcript><audio_57>persist your settings across sessions in earlier versions once you restarted it would go back to your original settings but in 2.4 you can persist any changes that you make over restarts which is kind of neat so here's an example balancer setting</transcript><transcript><audio_58>you define a cluster with one or more back-end servers and then you proxy pass to that balancer you can also specify different load factors if if one of the servers is more powerful than another and you want to</transcript><transcript><audio_59>send more content more data there more requests there rather see mod proxy documentation for the full list of options there are many different options about how you can load balance you can load balance based on number of</transcript> those back-end servers can be running http ftp or ajp and ajp is what tomcat talks so you can use this as a front-end for any of those servers they don't have to be there's also a new module in 2-4 called mod heartbeat and mod heart monitor so heartbeat runs on the back end heart monitor runs on the front end and it ensures that servers are still alive if they aren't alive then they get and as i mentioned you can use mod proxy there's also a balancer manager which is a web-based front-end to the to the balancer so you can configure various settings on the balancer through that web interface and i realized right before my talk that i have a very old screenshot of this but if you can imagine it being exactly like this only it allows you to do neat things like add additional workers into the process if you bring up a new server on the back end you can add that in you can also persist your settings across sessions in earlier versions once you restarted it would go back to your original settings but in 2.4 you can persist any changes that you make over restarts which is kind of neat so here's an example balancer setting you define a cluster with one or more back-end servers and then you proxy pass to that balancer you can also specify different load factors if if one of the servers is more powerful than another and you want to send more content more data there more requests there rather see mod proxy documentation for the full list of options there are many different options about how you can load balance you can load balance based on number of
{"source": "grass-yt-cc-by.1BjRbXBKRWk|shard_10013_19|create_multimodal_data.extract_yt_and_generate_transcripts.59|shard_10013|create_multimodal_data.generate_captions.59|shard_10013|create_multimodal_data.generate_captions.59", "params": {"id": "1BjRbXBKRWk", "channel_id": "UCLDJ_V9KUOdOFSbDvPfGBxw", "duration": 3362, "view_count": 1751, "age_limit": 0, "chapters": [{"start_time": 0, "end_time": 180.0, "title": "<Untitled Chapter 1>"}, {"start_time": 180.0, "title": "SERVER-INFO?CONFIG", "end_time": 266.0}, {"start_time": 266.0, "title": "COMMON WISDOM", "end_time": 380.0}, {"start_time": 380.0, "title": "BROWSER SUPPORT", "end_time": 477.0}, {"start_time": 477.0, "title": "ERROR LOGS", "end_time": 667.0}, {"start_time": 667.0, "title": "DOCUMENTATION", "end_time": 780.0}, {"start_time": 780.0, "title": "BALANCER MANAGER", "end_time": 830.0}, {"start_time": 830.0, "title": "EXAMPLE 2", "end_time": 852.0}, {"start_time": 852.0, "title": "LOADBALANCER PARAMETERS", "end_time": 1191.0}, {"start_time": 1191.0, "title": "SIMPLIFIED LOGGING", "end_time": 1438.0}, {"start_time": 1438.0, "title": "CHECKSPELLING", "end_time": 1589.0}, {"start_time": 1589.0, "title": "CACHING DYNAMIC CONTENT", "end_time": 1766.0}, {"start_time": 1766.0, "title": "COMPRESSED", "end_time": 1974.0}, {"start_time": 1974.0, "title": "SYSLOG", "end_time": 2229.0}, {"start_time": 2229.0, "title": "NORMAL LOGGING", "end_time": 2449.0}, {"start_time": 2449.0, "title": "SWITCH", "end_time": 2842.0}, {"start_time": 2842.0, "title": "PROTOCOL MODULES", "end_time": 3362}], "like_count": 6, "channel_follower_count": 18100, "license": "Creative Commons Attribution license (reuse allowed)", "uploader_id": "@communityovercode", "yt_tar_file": "/leonardo_work/EUHPC_E03_068/audio/fixed_download/grass-yt-cc-by//shard_10013/1BjRbXBKRWk.tar.gz"}}