Johannes Müller
07/13/2023, 1:46 PM#sudo docker-compose up docker_pipeline_code_location
docker_pipeline_code_location is up-to-date
Attaching to docker_pipeline_code_location
docker_pipeline_code_location | generating table # debug output from the running pipeline
...
This happens even though the schedule is configured explicitly with default_status=DefaultScheduleStatus.STOPPED
.
The code location fails to reload in dagit for the first 10 minutes with the error that it cannot be reached while it is running the pipeline.
Afterwards it works as expected.
Can I prevent the job from running when I reload the code location?
The Docker file looks like this:
...
# Run dagster gRPC server on port 4000
EXPOSE 4001
CMD ["dagster", "api", "grpc", "-h", "0.0.0.0", "-p", "4001", "-m", "customer_io"]
Zach
07/13/2023, 3:16 PM.execute_in_process()
or something similar at the global levelchris
07/13/2023, 5:02 PMJohannes Müller
07/14/2023, 6:07 AMJohannes Müller
07/14/2023, 6:07 AMJohannes Müller
07/14/2023, 2:51 PMJohannes Müller
07/14/2023, 2:52 PM