Sam Rausser
06/04/2020, 2:23 AMmax
06/04/2020, 2:28 AMSam Rausser
06/04/2020, 2:46 AMSam Rausser
06/04/2020, 2:47 AMmax
06/04/2020, 2:48 AMmax
06/04/2020, 2:49 AMSam Rausser
06/04/2020, 2:49 AMmax
06/04/2020, 2:50 AMmax
06/04/2020, 2:51 AMSam Rausser
06/04/2020, 2:51 AMSam Rausser
06/04/2020, 2:51 AMSam Rausser
06/04/2020, 2:52 AMmax
06/04/2020, 2:52 AMSam Rausser
06/04/2020, 2:53 AMlocal_compute_log_manager
?Sam Rausser
06/04/2020, 2:53 AMmax
06/04/2020, 2:54 AMmax
06/04/2020, 2:55 AMlsof
and ps
or equivalent and see if they see either an abnormal number of open files or a large number of python processesmax
06/04/2020, 2:55 AMmax
06/04/2020, 2:56 AMSam Rausser
06/04/2020, 2:58 AMSam Rausser
06/04/2020, 2:58 AMSam Rausser
06/04/2020, 2:58 AMSam Rausser
06/04/2020, 3:00 AMSam Rausser
06/04/2020, 3:00 AMmax
06/04/2020, 3:03 AMSam Rausser
06/04/2020, 3:05 AM0.7.13
max
06/04/2020, 3:05 AMmax
06/04/2020, 3:05 AMSam Rausser
06/04/2020, 3:05 AMcompute_logs
section from prod yaml file?max
06/04/2020, 3:06 AMcompute_logs:
module: dagster.core.storage.local_compute_log_manager
class: NoOpComputeLogManager
max
06/04/2020, 3:06 AMSam Rausser
06/04/2020, 3:10 AMSam Rausser
06/04/2020, 3:15 AMmax
06/04/2020, 3:26 AMalex
06/04/2020, 1:34 PMthey run as soon as they get 15-25k messages from kafkawhat exactly is the set up for kicking off pipeline runs? If the kafka listener is a long lived process its possible the issue is a memory / file descriptor leak from accidentally holding on to references
Sam Rausser
06/04/2020, 2:45 PM