[FEATURE] Prefer workload set-up to use the default durability mode

[Bukhtawar]

Is your feature request related to a problem?

Most production systems use index.translog.durability: request which is also the default to avoid silent data loss. With remote backed storage we disable the use of index.translog.durability: async to provide stronger durability semantics. As the result certain configurations fail to run these common benchmarks due to failures in creating an index with conflicting settings

opensearch-benchmark-workloads/big5/index.json

Lines 21 to 25 in 5de2e2f

	"index.codec": "best_compression",
	"index.translog.sync_interval": "30s",
	"index.translog.durability": "async",
	"index.query.default_field": [
	"message"

What solution would you like?

Avoid the use of non-recommended durability mode.

What alternatives have you considered?

Stay status quo

Do you have any additional context?

Add any other context or screenshots about the feature request here.

[IanHoang]

@gkamat Any thoughts on this?

[gkamat]

This should ideally be parameterized so the user can select either the request mode or async. We'll likely leave the default as async, since the workload is intended to evaluate performance, and is not in itself a production use-case. The user can currently override it by specifying the index settings, but that might be cumbersome.