[FTR] Session Concurrency Test

[elena-shostak]

Summary

Set security.session.cleanupInterval to 5h for session concurrency test.

Prerequisites

• Task for session cleanup with default schedule set to 1h.
• Task polling interval is set to 3000ms.
• We override scheduledAt once we make a request in runCleanupTaskSoon.

Hypothesis

Taking into consideration that:

• session_cleanup task is not the only one scheduled during test run.
• There is sort of an exponential backoff implemented for task polling if there are too many retries.
• Clock jitter.

I had a hypothesis that if our whole test run exceeds 1h or polling interval gets adjusted because of retries we might end up executing the scheduled cleanup before we trigger runCleanupTaskSoon (this is there we drop 1 session already).

FTR runs (x55 each)

• cleanupInterval set to 5h: #1 🟢, #2 🟢
• cleanupInterval set to default 1h: #1 🟢, #2 🔴 (has 2 failures out of 55)

Checklist

• Flaky Test Runner was used on any tests changed

For maintainers

• This was checked for breaking API changes and was labeled appropriately

Fixes: #149091

[elena-shostak]

/ci

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: aad5faa

Metrics [docs]

✅ unchanged

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

[elasticmachine]

Pinging @elastic/kibana-security (Team:Security)