instructions for how to force a node to be the tail

bcab97cb41708246499307df42bf12c54645b030 · 2024-07-17 15:00:23 -0700 · Alex Cheema

Files touched

M README.md

Diff

commit bcab97cb41708246499307df42bf12c54645b030
Author: Alex Cheema <41707476+AlexCheema@users.noreply.github.com>
Date:   Wed Jul 17 15:00:23 2024 -0700

    instructions for how to force a node to be the tail
---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 07dd4702..4a5d3482 100644
--- a/README.md
+++ b/README.md
@@ -98,7 +98,7 @@ That's it! No configuration required - exo will automatically discover the other
 
 The native way to access models running on exo is using the exo library with peer handles. See how in [this example for Llama 3](examples/llama3_distributed.py).
 
-exo also starts a ChatGPT-compatible API endpoint on http://localhost:8000. Note: this is currently only supported by tail nodes (i.e. nodes selected to be at the end of the ring topology). Example request:
+exo also starts a ChatGPT-compatible API endpoint on http://localhost:8000. Note: this is currently only supported by tail nodes (i.e. nodes selected to be at the end of the ring topology). If you want to force a node to be the tail, set its node-id to be sorted last alphabetically on start e.g. `python3 main.py --node-id xxxnode-mac-mini" Example request:
 
 ```
 curl http://localhost:8000/v1/chat/completions \

← eb92da2c cleaner chatgpt api impl with async callbacks · back to Exo · replace the ring topology image as it was not rendering some c432871e →