AlexKordic
AlexKordic
Can't really help, I have forgotten all the details about this issue.
Can't really help, I have forgotten all the details about this issue.
Can't really help, I have forgotten all the details about this issue. On Tue, May 6, 2014 at 12:10 PM, alfred-dev [email protected]: > Is this still relevant? I dont get...
Couldn't reproduce the crash
Tested on nvidia card with: ``` go run cmd/livepeer/livepeer.go --datadir=/home/alex/temp/livepeer/TEST_T1 --transcoder=true --orchSecret=foo --orchAddr="127.0.0.1:18935" --cliAddr=":17936" --nvidia=0 --v=6 ```
We chosen gRPC because it is already used in BOT. In direct MistT scenario we can reconsider using websocket.
Solution 2 looks better in the long run
Update on solution-2: Redirection for streaming workflow. It is tracked [here](https://github.com/livepeer/go-livepeer/issues/2531). Streaming workflow uses `websocket` protocol. On initial connect redirect allows for load-balancing of Orchestrator cluster. Horizontal scaling of orchestrators...
PR created https://github.com/livepeer/catalyst-api/pull/17
First step: add S3 support to [URIReader::open(const HTTP::URL &uri)](https://github.com/DDVTECH/mistserver/blob/master/lib/urireader.cpp#L47)