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.

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

leader container maxing CPU #27

Open
Ephron-WL opened this issue Jan 15, 2025 · 1 comment
Open

leader container maxing CPU #27

Ephron-WL opened this issue Jan 15, 2025 · 1 comment
Assignees
Labels
bug Something isn't working

Comments

@Ephron-WL
Copy link

I ran your sample project. It seemed to work well. Congratulations on excellent work.

I did notice the leader container maxing CPU. I discovered the RaftLeaderState loop never enters the idle state. I attribute it to an invalid operator, but you might want to verify.

idleRun &= await TryApplyLogs().ConfigureAwait(false);

To:?

idleRun |= await TryApplyLogs().ConfigureAwait(false);

For testing the sample project, running a LoadBalancer instead of NodePort seemed to work better for me. I was then able to make the API calls more easily from my dev environment.

curl -X POST http://localhost:8080/Counter/Increment
curl http://localhost:8080/Counter

If you'd like me to PR these changes, let me know, considering that the changes are minor. Otherwise, I can later when I get the DNS thing figured out.

@zarusz
Copy link
Owner

zarusz commented Jan 15, 2025

Thank you! Yes, good points. Happy to accept a PR with the improvements.

@zarusz zarusz added the bug Something isn't working label Jan 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants