akatona84 commented on PR #13733: URL: https://github.com/apache/kafka/pull/13733#issuecomment-1556885401
I just wrote down my motivation to exclude unreadable ones from plugin path. This specific case can be easily solved with better dir organizing. But you made me think what I really wanted. :) IMO the issue is around skipping ALL plugins (or at least the following ones after the faulty) to be loaded whenever there's a bad one. And not failing the startup, just ignoring them all. (in my case mm2 relied on a config provider plugin hence it failed to start) With the current code if an admin is adding a plugin wrong the connect cluster can startup but the connectors/config providers will fail. So either - we should fail the herder startup entirely OR - do the error handling properly, per plugin. I'm overwriting the PR aiming this behavior, and curious what you guys think about it and my argument. -- 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]
