Skip to content
New issue

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

Sign up for GitHub

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

Already on GitHub? Sign in to your account

Jump to bottom

Decouple the RaftNode.run asynchronous task from tick #102

Open
jopemachine opened this issue May 10, 2024 · 0 comments
Open

Decouple the RaftNode.run asynchronous task from tick #102

jopemachine opened this issue May 10, 2024 · 0 comments
Labels
epic improvement

Comments

@jopemachine
Copy link
Member

jopemachine commented May 10, 2024 •
edited
Loading

In the current structure, all APIs are forced to be async, and since RaftNode.run is the only one that owns RaftNode, all APIs are unnecessarily coupled with the task.

Let's change this structure and convert unnecessary async functions to sync.
@jopemachine jopemachine changed the title Decoupling the RaftNode.run asynchronous task from tick. Decoupling the RaftNode.run asynchronous task from tick May 10, 2024
@jopemachine jopemachine changed the title Decoupling the RaftNode.run asynchronous task from tick Decouple the RaftNode.run asynchronous task from tick May 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
epic improvement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jopemachine