I'm trying to use the settings API to set index.translog.disable_flush
to true and backing up elasticsearch data afterwards.
I'm using the local gateway as configured by default.
Setting the disable_flush parameter will produce a log output telling
me that the option might be accepted by each index.
If I start some indexing operations after that, I can see filesystem
activity inside the index and translog directories of the index data.
I was expecting no filesystem activity in this place with flush
Does that mean, translog data are written to the filesystem even if
flush is disabled?
If this is the case, backing up the whole data directory may produce
warnings by the backup software that files have been changed during
the backup process. Such warnings could be ignored trusting
elasticsearch to ignore such files during a cluster restart from
backup as well.
To avoid such warnings, it would be handy to have inclusion or
exclusion patterns in place for backing up the data directory.
Is it it possible to provide such patterns?