SEZ9 commented on issue #12734: URL: https://github.com/apache/seatunnel/issues/12734#issuecomment-6137863218
Thanks for the clear analysis and proposed fix — this looks like a genuine bug rather than a question, so it makes sense to treat it as one. The retry-and-unblacklist direction is reasonable, and the guidance already given in this thread stands: keep the first fix minimal, reuse the joiner's existing retry cadence instead of introducing a new user-facing property, limit the change to lite members so the regular member self-election path is untouched, and add the coverage already outlined (worker starting first and joining once a master appears before `hazelcast.max.join.seconds`; worker with no master ever available still timing out without self-electing; unchanged non-lite path; and the discovery joiner subclass). Only clear the temporarily blacklisted addresses, not permanently blacklisted ones. A PR against `dev` is welcome — please link it here once it's open. <!-- streview-comment:1721 --> -- 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]
