You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please note that this issue tracker is not a help form and this issue will be closed.
Before submitting, please ensure you have gone through our documentation.
Question
Is it possible to tell or fill in at runtime which scheduler gets used in component logic? For example, if I have a ddp component, within the component, before I return specs.AppDef, can I set for example a macro that would tell me which scheduler this component gets ran with?
For example, I want to be setting some environment variables but differentiate based on which scheduler gets used.
The text was updated successfully, but these errors were encountered:
For example, if I want component level behavior specific to local schedulers (local, docker), I could for example add an additional redundant parameter --local in the component to specifiy that logic. But I can stick with default behavior for cloud based scheduler, like aws, gcp, etc...
Instead, wondering if it is possible to determine the scheduler from the component and define behavior there for specific schedulers, rather than vice versa. In this way, I can modify the component rather than multiple different schedulers.
Otherwise the only place where this scheduler metadata is propogated is ENV TORCHX_JOB_ID as part of runner api,
❓ Questions and Help
Please note that this issue tracker is not a help form and this issue will be closed.
Before submitting, please ensure you have gone through our
documentation.
Question
Is it possible to tell or fill in at runtime which scheduler gets used in component logic? For example, if I have a ddp component, within the component, before I return specs.AppDef, can I set for example a macro that would tell me which scheduler this component gets ran with?
For example, I want to be setting some environment variables but differentiate based on which scheduler gets used.
The text was updated successfully, but these errors were encountered: