Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually?

Hi @hanbj, we have found your signature in our records, but it seems like you have signed with a different e-mail than the one used in yout Git commit. Can you please add both of these e-mails into your Github profile (they can be hidden), so we can match your e-mails to your Github profile?

Hi @hanbj , may I ask how you found out about this? Was this a problem that you ran into or something that you noticed while looking at the code?

jenkins test this please

@javanna Thank you for verifying the patch, I found this when I read the code

@karmi I'm sure I've always used this email on GitHub. How can I have a different signature?

(1018a11)
@javanna Accidentally put together, please test together, thank you.
When you build the FixedExecutorBuilder instance, the parameter availableProcessors is passed in the construction method. Therefore, there is no need to calculate once in the applyHardSizeLimit() method

@hanbj, this commit was failing the check, dbd6206

I think you should git rebase instead of merge the upstream commits, that way the PR is cleaner to read...

@karmi OK, Thanks. I resubmit it.

#26070 #26068
@karmi I'm sorry to trouble you. I resubmit it. Thank you