kontrollanten

Here's the full information about the jobs: ``` [ { "id": "173", "state": "completed", "type": "video-transcoding", "data": { "type": "optimize-to-webtorrent", "videoUUID": "0723eff8-e93e-4567-b645-17db0437878f" }, "progress": 100, "priority": 138, "error": null, "createdAt":...

I'm sorry but I can't see if that where the case. May the high CPU usage be the cause of the tripled jobs?

Okay. We've a separate server where redis is running, is it that server that needs more CPU? Is it possible to retry later if `Missing lock for job` is thrown?...

This happened again for a work running 21:37:18 to 21:49:41:

May be related to this: Yesterday we found that a video transcoded 18th July didn't work for resolution 240 and 720. The playlists for each resolution returned 404. When looking...

> May be related to this: > > Yesterday we found that a video transcoded 18th July didn't work for resolution 240 and 720. The playlists for each resolution returned...

No, I don't know what happened. Redis is only used for PeerTube, so it's PT related. There hasn't been any peaks like that since then, we'll run some transcoding later...

# Case study Here's a case study for one video which where broken, not sure if was related to original topic, but probably. ## Initial transcoding During initial transcoding three...

> * Server files should not change since you only use existing server methods How should we get the playlist name and short uuid then? It sounds inefficient to do...

Another use case: 1. In the browser dev tools: block the URL for a fragments file for a specific resolution 2. Watch the video In this case the player just...