[Infra] Internal Server Error returns when accessing the Hosts landing page having set the search period out of the boost window

[ablnk]

Description:
GET /api/metrics/infra/host request fails with status code 500 and returns "Request timed out" when accessing the Hosts landing page having set the search period out of the boost window.

{
    "statusCode": 500,
    "error": "Internal Server Error",
    "message": "Request timed out",
}

The issue is only reproducible in a test LogsDB environment with search power set to 35.

Data in the search period:

Data view	Docs
Logs	2,732,575,843
Metrics	601,310,529
Metrics - Kubernetes	261,604,394
APM	1,005,652,761

Looks similar to #195882 but for this one I haven't found related logs.

Steps to reproduce:

1. Go to Infrastructure - Hosts.
2. Set the search period 7 days outside the boost window.
3. Verify that hosts metrics are loaded.

Expected behavior:

Hosts metrics are loaded.

[elasticmachine]

Pinging @elastic/apm-ui (Team:APM)

[elasticmachine]

Pinging @elastic/obs-ux-infra_services-team (Team:obs-ux-infra_services)

[gbamparop]

The issue is only reproducible in a test LogsDB environment with search power set to 35.

@ablnk since this is for metrics in the host landing page, is it related to LogsDB?

[chrisdistasio]

I believe we've ruled out changing SP to 35 and are defaulting to a # of 45. @cachedout can you please confirm?