pegasas commented on issue #15330: URL: https://github.com/apache/dolphinscheduler/issues/15330#issuecomment-1869961927
Thanks wenjun. These days I've been thinking the relationship of trigger & scheduler service responsibility in new architecture. In my current high-level design. 1. host 2 trigger related table: trigger -> trigger instance, which currently may be host by quartz scheduler 2. Push: HTTPTrigger -> push -> create trigger instance 3. Pull: ThreadPool -> pull -> onevent -> create trigger instance Pull mode is more common and needs resource, I am thinking integrate pull trigger into a special task type, which could be dispatched by master/worker, leverage current task architecture which can master/server failover. Scheduler: pull trigger instance on this master host -> command -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
