You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Because of #1651, we introduced #1684 as a temporary workaround. With #1651 being fixed now, we can remove the temporary solution which introduced a start-up dependency on the ingress which needed all partitions having an actively running leader.
The text was updated successfully, but these errors were encountered:
…ost SubmitNotifications
With restatedev#1651 being fixed, we no longer need to wait for all partitions to have a
running leader before we can start the ingress to avoid stucks invocations. That's
because the ingress will now retry until it finds an active leader for a given partition.
This fixesrestatedev#2206.
Because of #1651, we introduced #1684 as a temporary workaround. With #1651 being fixed now, we can remove the temporary solution which introduced a start-up dependency on the ingress which needed all partitions having an actively running leader.
The text was updated successfully, but these errors were encountered: