The create collection coordinator must store the timeseries options in the shading catalog collection entry. These options could be either passed directly from the driver or if the collection already exists should be inherited from the local catalog.

While translating the request parameters, the coordinator calculates the target timeseries options by fetching existsing ones from the local catalog. The problem is that the calculated timeseries options are being stored in the in-memory representation of the original request, but not persisted in the coordinator doc.

Later on, in the commit phase, the coordinator fetches back the timeseries options from the in-memory representation of the original request.

This means that if a stepdown happens after calculating the target timeseries options but before the commit phase consume them. It could be that the calculated options get lost and we will simply use the original options coming from the request.

One possible solution would be to store the target timeseries options in the TranslatedRequestParams and ensure we persist them on disk before entering the commit phase.