Vipul Goswami09/24/2023, 8:18 PM
After registering the task i have also activated the plan using following command:
@task( requests=Resources(cpu="100m", mem="50Mi"), limits=Resources(cpu="200m", mem="1Gi"), ) def print_task(): print("This is a test print") @workflow( failure_policy=WorkflowFailurePolicy.FAIL_AFTER_EXECUTABLE_NODES_COMPLETE, ) def wf_test(): print_task() LaunchPlan.get_or_create( name="Scheduler_test", schedule=FixedRate(duration=timedelta(minutes=4)), workflow=wf_test, )
But this code runs perfectly fine in my Local but as soon i deploy the setting to our EKS cluster in AWS, i dont see that the event get fired automatically. But then i came across this page : https://docs.flyte.org/projects/cookbook/en/latest/auto_examples/productionizing/lp_schedules.html#platform-configuration-changes-for-aws-scheduler Where it has mentioned that we might need to setup the SQS and Workflow Executer to make the scheduler work. Is that my understanding correct because just above that line it says
flytectl update launchplan -p flyte-test -d main Scheduler_test --version m8ZSwKhjiI3fpEJwElYx4A== --activate
and also i would like to know which place does this line is pointing to :
You can still run the Flyte native scheduler on AWS.
Appreciate your help and input. 🙏 1st Image local 2nd image from AWS
To run workflow executions based on user-specified schedules, you'll need to fill out the top-level scheduler portion of the flyteadmin application configuration.
Vipul Goswami09/25/2023, 7:31 AM
Vipul Goswami09/25/2023, 10:16 AM
Vipul Goswami09/25/2023, 12:35 PM
workflow_scheduler: enabled: false
Vipul Goswami09/25/2023, 12:57 PM
Vipul Goswami09/25/2023, 1:01 PM