lm-sys / lm-sys/FastChat

Support for htttps protocol call between controller node and worker node

Open
#1,915 4 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

good first issue
Dominant language
Python
Stars
39.5k
Forks
4.8k
PR merge metrics
No merged PRs in 30d

Description

Hi team,

Thanks for the great work. Recently, we are trying to set up a large-scale chatbot service. Our case is like: We have a controller server node where we can set up a web application; we have another server which contains 8 gpus to run the model instances. However, the GPU server we have can only support the https calls rather than http calls because only the default 443 https port can be opened to listen. We tried to enable the controller to call the https 443 port of GPU server node and the following error was received on controller node server:

Get status fails: https://GPU_Server_ip:443, HTTPSConnectionPool(host='GPU_Server_ip', port=443): Max retries exceeded with url: /worker_get_status (Caused by SSLError(SSLError(1, '[SSL: WRONG_VERSION_NUMBER] wrong version number (_ssl.c:1131)')))

Is there anyway we can use htttps call to get the message from the server?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the controller's worker status request and the worker node's listener; the issue does not identify the relevant files or tests. Verify how the current HTTP call is configured and whether TLS is supported on the worker endpoint; done means the controller can retrieve worker status through HTTPS on port 443.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend, networking
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.