matthewwalker1621-star commented on issue #17917: URL: https://github.com/apache/dolphinscheduler/issues/17917#issuecomment-4106631686
Thanks for bringing this to attention On Sun, Mar 22, 2026, 8:55 AM SHRIHARI KULKARNI ***@***.***> wrote: > *shrihari7396* left a comment (apache/dolphinscheduler#17917) > <https://github.com/apache/dolphinscheduler/issues/17917#issuecomment-4106298095> > > Hi @ruanwenjun <https://github.com/ruanwenjun>, > > I wanted to share the approach I am planning to take for embedding the > AlertServer into the API Server and get your feedback. > > The idea is to integrate the alert module directly into the API process > and remove the RPC layer, so alert execution happens via direct in-process > method calls. > > For handling multi-instance deployments, I am planning to reuse the > existing AlertHAServer mechanism so that only the ACTIVE API node runs the > AlertEventLoop (polling + dispatch), while other nodes remain in standby. > Stateless operations like "Test Send" will still be available on all nodes. > > To ensure isolation: > > - I plan to use a dedicated thread pool for alert processing, separate > from API request threads. > - For plugin loading, I am considering using SPI (ServiceLoader) along > with isolated URLClassLoaders per plugin JAR to avoid dependency conflicts > and ensure proper isolation. > > Does this approach align with the expected design, or is there an existing > pattern in DolphinScheduler that I should follow for plugin loading and > isolation? > > Thanks! > > — > Reply to this email directly, view it on GitHub > <https://github.com/apache/dolphinscheduler/issues/17917?email_source=notifications&email_token=B7GHLXAYBPIB4K7MK5454X34R7WFHA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIMJQGYZDSOBQHE22M4TFMFZW63VKON2WE43DOJUWEZLEUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#issuecomment-4106298095>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/B7GHLXBZ3S2DCAZROSWSXTD4R7WFHAVCNFSM6AAAAACTJQAZ6CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DCMBWGI4TQMBZGU> > . > You are receiving this because you are subscribed to this thread.Message > ID: ***@***.***> > -- 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]
