chore(runtime): log thread pool settings

[yordis]

• Operators need startup evidence when runtime thread-pool limits are changed so queue behavior can be diagnosed from logs.

[cursor]

PR Summary

Low Risk
Low risk: behavior remains setting ThreadPool max threads to 1000; change mainly adds logging and a warning if configuration fails.

Overview
Moves the ThreadPool.SetMaxThreads(1000, 1000) call into a new ConfigureThreadPool() helper invoked during startup after logging initialization.

ConfigureThreadPool() captures min/max worker and completion-port thread counts before/after configuration, logs the deltas, and emits a warning if SetMaxThreads fails.

^{Reviewed by Cursor Bugbot for commit c2fea70. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit aa90809. Configure here.}

[coderabbitai]

Warning

Rate limit exceeded

@yordis has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 48 minutes and 55 seconds before requesting another review.

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: c212c76d-a421-445f-b938-f3deb0c64ece

📥 Commits

Reviewing files that changed from the base of the PR and between aa90809 and c2fea70.

📒 Files selected for processing (1)

• src/EventStore.ClusterNode/Program.cs

Walkthrough

Program.cs extracts thread pool configuration into a dedicated ConfigureThreadPool() helper method that captures and logs diagnostic information. The Main method invokes this helper instead of directly calling ThreadPool.SetMaxThreads(). The helper reads current min/max thread counts, applies the configuration change, and logs before/after values.

Changes

Thread Pool Configuration Refactoring

Layer / File(s)	Summary
Thread pool setup with logging src/EventStore.ClusterNode/Program.cs	New ConfigureThreadPool() helper method reads current thread pool min/max values for worker and completion port threads, sets max threads to 1000, and logs diagnostic before/after state. Main invokes this helper instead of setting thread pool limits directly.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~5 minutes

Poem

A rabbit hops through the code with glee, 🐰
Threading helpers now logged for all to see,
Before and after, the diagnostics flow,
Configuration extracted—how it should go!

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: adding logging for thread pool settings during startup configuration.
Description check	✅ Passed	The description explains the rationale for the change: operators need startup evidence of thread pool limit changes for diagnostics.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch yordis/chore-log-threadpool-settings

Warning

Review ran into problems

🔥 Problems

Git: Failed to clone repository. Please run the @coderabbitai full review command to re-trigger a full review. If the issue persists, set path_filters to include or exclude specific files.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@src/EventStore.ClusterNode/Program.cs`:
- Line 452: ThreadPool.SetMaxThreads can fail silently; capture its bool return
value where Program calls ThreadPool.SetMaxThreads and check it, then emit a
clear error log (using the existing program logger or Console.Error) if it
returns false and take appropriate action (e.g., throw or exit) so operators can
see the configuration failed; specifically, replace the raw
ThreadPool.SetMaxThreads(...) call with a bool result =
ThreadPool.SetMaxThreads(...); if (!result) log an error mentioning
"ThreadPool.SetMaxThreads failed" and include the attempted values and fail fast
or handle the error as the surrounding Program/Main logic requires.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 3800430a-961f-48fe-b114-ac449ad84c8f

📥 Commits

Reviewing files that changed from the base of the PR and between d552b3e and aa90809.

📒 Files selected for processing (1)

• src/EventStore.ClusterNode/Program.cs