Assertion Updates Needed due to esarchiver load action concurrency change - x-pack/test/monitoring_api_integration/apis/elasticsearch/indices.ts

[wayneseymour]

The es archiver load action is being updated to increase speed.

The usual culprit is the concurrency, which places data out of expected sort order.
We expect placing a sort order in the queries themselves is one solution.
Another could be asserting in such a fashion that does not require a sort order.

The tests were commented out in the index file.

This is issue is an attempt to ensure that no decreased coverage, goes overlooked.

[klacabane]

Thanks for the issue @wayneseymour! Do we have a way to control concurrency from the client or the option can only be controlled internally ?

[elasticmachine]

Pinging @elastic/infra-monitoring-ui (Team:Infra Monitoring UI)

[wayneseymour]

Thanks for the issue @wayneseymour! Do we have a way to control concurrency from the client or the option can only be controlled internally ?

No, we do not. Is that something you would like?