79ef0b89e4
We've noticed that when nodes have connection problems, they get full segments with different hashes. Inspection of these segments shows that they all have identical data up to a point. Segments that fetched normally will then have the remainder of the data. Segments that had issues will have a slightly corrupted end. The data is still valid, and no errors are raised. It just doesn't have all the data. We noticed that these corrupted segments all were cut off exactly 60sec after their requests began. We believe this is a server-side timeout on the request that returns whatever data it has, then closes the container file cleanly before returning successfully. We detect segments that take > 59 seconds to recieve, and label them as "suspect". Suspect segments are treated identically to partial segments, except they are always preferred over partials. |
5 years ago | |
|---|---|---|
| backfiller | 5 years ago | |
| common | 5 years ago | |
| cutter | 5 years ago | |
| db_scripts | 5 years ago | |
| downloader | 5 years ago | |
| monitoring | 5 years ago | |
| nginx | 5 years ago | |
| postgres | 5 years ago | |
| restreamer | 5 years ago | |
| segment_coverage | 5 years ago | |
| sheetsync | 5 years ago | |
| thrimbletrimmer | 5 years ago | |
| thrimshim | 5 years ago | |
| .gitignore | 6 years ago | |
| .travis.yml | 5 years ago | |
| DATABASE.md | 5 years ago | |
| INSTALL.md | 5 years ago | |
| LICENSE | 5 years ago | |
| README.md | 5 years ago | |
| SecurityModel.md | 5 years ago | |
| build | 5 years ago | |
| docker-compose.jsonnet | 5 years ago | |
| generate-docker-compose | 5 years ago | |
| generate-flamegraph | 6 years ago | |
| get-build-tag | 5 years ago | |
| initial-design-doc.pdf | 6 years ago | |
README.md
Wubloader is a system for saving, re-serving and cutting into videos of a target twitch (or probably other HLS, but some twitch specifics are assumed) stream.
It was designed to serve the needs of the Video Strike Team as part of Desert Bus For Hope.
A full design doc can be read at initial-design-doc.pdf, but a brief overview of the components:
downloadergrabs segments from twitch and saves them to diskrestreamerserves segments from disk as well as playlist files allowing them to be streamedbackfillerqueries restreamers of other servers in order to pick up segments this server doesn't have already, ie. it replicates missing segments.cutterinteracts with a database to perform cutting jobssheetsyncsyncs specifc database columns to a google doc which is the primary operator interface.thrimshimacts as an interface between thethrimbletrimmereditor and the database.thrimbletrimmeris a browser based video editor.segment_coverageregularly checks whether there is complete segment coverage for each hour.databasehosts a Postgres database to store events to be edited.nginxprovides a webserver through which the other components are exposed to the outside world.commonprovides code shared between the other components.monitoringprovides dashboards to allow the wubloader to be monitored.
Usage
All components are built as docker images.
Components which access the disk expect a shared directory mounted at /mnt.
A docker-compose file is provided to run all components. See docker-compose.jsonnet
to set configuration options, then generate the compose file with ./generate-docker-compose.
Then run docker-compose up.
Further details of installing and configuring the backfiller are provided in INSTALL.md.