-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: hosts for replicas #2338
feat: hosts for replicas #2338
Conversation
Codecov Report
@@ Coverage Diff @@
## master #2338 +/- ##
==========================================
+ Coverage 89.77% 90.86% +1.09%
==========================================
Files 222 222
Lines 11958 12013 +55
==========================================
+ Hits 10735 10916 +181
+ Misses 1223 1097 -126
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
Latency summaryCurrent PR yields:
Breakdown
Backed by latency-tracking. Further commits will update this comment. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think to have hosts for different Pods in the CompoundPod we need another layer of arguments.
We could start by adding replica hosts, to allow every replica to be on one host, and then maybe consider different hosts for every Pea of every replica
With this implementation, every pea can have its own host. |
but what about different Peas of different Replicas? |
|
My biggest concern is, that the new pattern of havinf CompoundPod just a composition of Pods is not so well defined. |
Interesting - a timeout again. I will investigate what it is caused by. |
@JoanFM is there anything left to do for me? |
args = set_pod_parser().parse_args( | ||
[ | ||
'--name', | ||
'pod', | ||
'--parallel', | ||
'2', | ||
'--replicas', | ||
'3', | ||
'--peas-hosts', | ||
*[f'0.0.0.{i+1}' for i in range(num_hosts)], | ||
'--runtime-backend', | ||
'process', | ||
] | ||
) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you try to convert one of the functional integration tests (CRUD etc.) to use this approach, to see that the ops work properly in this new setup?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
one request
* feat: hosts for replicas * feat: hosts for replicas cleanup * test: fix same ports * refactor: abstract base method * refactor: more readable
closes #2339