0-u-0 / dugon-media-server Goto Github PK

dugon-media-server 中包含了一个worker，通常跑在一个cpu核心上；当会议规模足够大时，这个worker会因有过多的consumer（无论worker中包含几个router）而压力暴增，最终会打爆单核。简单看下，在当前项目中，并没有涉及这个问题的解决，请问有相关的计划吗？

Hi can I know the purpose of the project? I'm looking at a simple to use media server.

1、看到你有计划使用 pion/webrtc 来重写 media-server ，但 pion 的性能我有点担心，mediasoup 的底层是基于 google webrtc lib 的 c++ 实现，应该对性能更有保障？
2、比如天南海北共100个人，参加同一个会议，我在东南西北四个机房各部署多个 dugon-media-server 和 dugon-signal-server 实例，用户接入时，我按地域来调度到对应区域的 server。那么对于一个"房间/会议"，该房间的信令和媒体能力都是跨域的多个 server 共同提供的吧？分布式？
3、 欢迎 pr 共同开发吗？

十分感谢！

你好，我按照你的方法尝试在Ubuntu18.04与14.04上运行(node版本12.18.3)，均出现了同一个问题:

[email protected] start /opt/dugon-media-server
node main.js

[ INFO ] |2020-10-14 13:42:12| main - Config -> debug: true, id: foo, area: jp, host: tokyo1, name: test, nats: [Object], ip: 127.0.0.1, publicIp: 127.0.0.1, port: [Object], monitor: 0, log: [Object]
[ INFO ] |2020-10-14 13:42:12| main - Nats -> nats://127.0.0.1:4222
[ INFO ] |2020-10-14 13:42:12| main - UDP port range -> min: 40000, max: 49999

events.js:292
throw er; // Unhandled 'error' event
^
NatsError: Could not connect to server: Error: connect ECONNREFUSED 127.0.0.1:3333
at Socket. (/opt/dugon-media-server/node_modules/nats/lib/nats.js:833:26)
at Socket.emit (events.js:315:20)
at emitErrorNT (internal/streams/destroy.js:92:8)
at emitErrorAndCloseNT (internal/streams/destroy.js:60:3)
at processTicksAndRejections (internal/process/task_queues.js:84:21)
Emitted 'error' event on Client instance at:
at Socket. (/opt/dugon-media-server/node_modules/nats/lib/nats.js:833:12)
at Socket.emit (events.js:315:20)
[... lines matching original stack trace ...]
at processTicksAndRejections (internal/process/task_queues.js:84:21) {
code: 'CONN_ERR',
chainedError: Error: connect ECONNREFUSED 127.0.0.1:3333
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1141:16) {
errno: 'ECONNREFUSED',
code: 'ECONNREFUSED',
syscall: 'connect',
address: '127.0.0.1',
port: 3333
}
}
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: node main.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2020-10-14T05_42_12_344Z-debug.log
在centos7上尝试运行也出现了如下问题(node版本12.19.0)：

[email protected] start /usr/src/dugon-media-server
node main.js

[ INFO ] |2020-10-14 13:43:01| main - Config -> debug: true, id: foo, area: jp, host: tokyo1, name: test, nats: [Object], ip: 127.0.0.1, publicIp: 127.0.0.1, port: [Object], monitor: 0, log: [Object]
[ INFO ] |2020-10-14 13:43:01| main - Nats -> nats://127.0.0.1:4222
[ INFO ] |2020-10-14 13:43:01| main - UDP port range -> min: 40000, max: 49999
(node:2601) UnhandledPromiseRejectionWarning: Error: [pid:2622, code:1, signal:null]
at ChildProcess. (/usr/src/dugon-media-server/node_modules/mediasoup/lib/Worker.js:117:43)
at ChildProcess.emit (events.js:314:20)
at Process.ChildProcess._handle.onexit (internal/child_process.js:275:12)
at Process.callbackTrampoline (internal/async_hooks.js:126:14)
(node:2601) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:2601) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
在多次尝试解决之后仍然没有改变，是否能提供更详细的安装说明，十分感谢

RT