Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

ZOOKEEPER-4898: FastLeaderElection WorkerSender/WorkerReceiver don't need to be Thread #2228

Merged
merged 2 commits into from
Feb 28, 2025

Conversation

ZLATAN628
Copy link
Contributor

WorkerSender inherits from ZooKeeperThread. When using WorkerSender, a WorkerSender thread is created first, followed by the creation of a new thread where WorkerSender is passed as a task. At this point, the ExceptionHandler in ZooKeeperThread does not take effect.

…d leads to the failure of exception handling
Copy link
Member

@kezhuw kezhuw left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am not sure why ZOOKEEPER-1810 introduced separated thread. But there are do differences in behavior in logging(jdk System.err vs slf4j LOG.info).

I am good to the direction. Also, it will supersede ZOOKEEPER-4884.

…d leads to the failure of exception handling
Copy link
Member

@tisonkun tisonkun left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for your contribution! LGTM.

@tisonkun tisonkun changed the title ZOOKEEPER-4898: The incorrect usage of the subclass of ZooKeeperThrea… ZOOKEEPER-4898: FastLeaderElection WorkerSender/WorkerReceiver don't need to be Thread Feb 28, 2025
@tisonkun tisonkun merged commit 1a9bcbd into apache:master Feb 28, 2025
14 checks passed
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants