In the analyze_shard_key.js concurrency test, the expiration time for split point docs is set to 30 seconds to avoid making recovery extremely slow in suites that do restarts. However, we sometimes see the agg request (running $_analyzeShardKeyReadWriteDistribution) take longer than the expiration secs on the split point documents - this means the read/write metrics can be off if some (or all) split point docs have already been deleted. If this happens, we can ignore the failed assertions - one way of doing this could be to track the duration of the analyzeShardKey command in the workload, and if it is longer than the splitPointExpirationSecs value, ignore the error thrown by assertReadWriteDistributionMetrics in isAcceptableAnalyzeShardKeyError.