🇺🇸United States @DigantDj

We ran into the same issue after Drupal core & module update, this will definitely. It would be helpful to solve for even if not at the per-entity level, at least at the root level for someone who wants to keep the legacy behavior of publish by default.

digantdj → created an issue.

Patch #49 works fine for me until there's auto-scaling(adding shards) & slot redtribution. I understand with pipeline we will get MOVED server error, but is there a way to handle & retry this? Otherwise it defeats the purpose of going for Cluster Enabled Elasticache if we can't autoscale.