Add shardTimeout params to body only if not 0

[markov00]

Summary

Fix #27209

Checklist

Use strikethroughs to remove checklist items you don't feel are applicable to this PR.

• [ ] This was checked for cross-browser compatibility, including a check against IE11
• [ ] Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
• [ ] Documentation was added for features that require explanation or tutorials
• [ ] Unit or functional tests were updated or added to match the most common scenarios
• [ ] This was checked for keyboard-only and screenreader accessibility

For maintainers

• [ ] This was checked for breaking API changes and was labeled appropriately
• ~[ ] This includes a feature addition or change that requires a release note and was labeled appropriately`

[elasticmachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request

[timroes]

Code LGTM, tested, that the fix doesn't set timeout anymore when elasticsearch.shardTimeout is 0

[elasticmachine]

Pinging @elastic/kibana-app

[elasticmachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request

[levinsond]

Not sure if here is the correct place for my question... Apologies in advance if it is not.
We have an ELK deployment in Elastic Cloud and we have some users analyzing data in Kibana. Since we upgraded to 6.5.4 a couple of days ago, we have had to restart the cluster several times due to Memory issues. We were doing fine with 4GB of memory but we decided to resize - upgrade to 8GB thinking this would solve the issue. It did not and we had to restart again today. Could this fix for 6.5.4 be related to our issue? I am not very technical, but I have access in Kibana to the administrator panel. Any suggestions?

[markov00]

@levinsond this issue fixes the timeout problem that occurs in cloud when using Kibana. Are you are you experiencing the same warning as described in #27209?
Have you already filed a support ticket? I think it's the best place to get the right answer for this question.

[levinsond]

In 6.5.3 we experienced the warning from #27209 constantly when using Kibana.
We upgraded to 6.5.4 and now we are having the memory issues described. I also opened a support ticket. Thanks!