open-webrtc-toolkit/owt-server

management-api log:Failed in scheduling portal worker, reason: No worker available, all in full load

zhcf opened this issue · 1 comments

zhcf commented

2022-08-10 18:17:27.895 - DEBUG: AmqpClient - Publish content: {"method":"schedule","args":["portal","50454856047",{"isp":"isp","region":"region"},60000],"corrID":439,"replyTo":"amq.gen-HOzV6z4XHh9Z2OjDfepWTw"}
2022-08-10 18:17:28.026 - DEBUG: AmqpClient - New message received { data: 'error',
corrID: 439,
type: 'callback',
err:
'Failed in scheduling portal worker, reason: No worker available, all in full load.' }
2022-08-10 18:17:28.026 - DEBUG: AmqpClient - Callback callback - error
2022-08-10 18:17:28.026 - INFO: RequestHandler - Faild in scheduling portal tokenCode: 50454856047 , keep trying.
2022-08-10 18:17:29.027 - DEBUG: AmqpClient - remoteCall, corrID: 440 to: owt-cluster method: schedule
2022-08-10 18:17:29.027 - DEBUG: AmqpClient - Publish content: {"method":"schedule","args":["portal","50454856047",{"isp":"isp","region":"region"},60000],"corrID":440,"replyTo":"amq.gen-HOzV6z4XHh9Z2OjDfepWTw"}
2022-08-10 18:17:29.116 - DEBUG: AmqpClient - New message received { data: 'error',
corrID: 440,
type: 'callback',
err:
'Failed in scheduling portal worker, reason: No worker available, all in full load.' }
2022-08-10 18:17:29.116 - DEBUG: AmqpClient - Callback callback - error

zhcf commented

The root cause is the workload of the server exceeds 0.85