HuK719

> @FinerKeysen hello, we can set the number of retries while passing the request to Upstream using the underlying Nginx mechanism. see: https://apisix.apache.org/docs/apisix/admin-api/#request-body-parameters-3 yes, i find this parameter in upstream...

> Upstream retries at the route level are not yet supported. will route level retry be supported in next version?

> > > Upstream retries at the route level are not yet supported. > > > > > > will route level retry be supported in next version? > >...

> You can refer to the [traffic-split](https://github.com/apache/apisix/blob/master/apisix/plugins/traffic-split.lua) plugin, set your own upstream, and dynamically set your retry parameters in the upstream. ok, i'll read and make a try

> I would like to know in what scenario support for route level upstream retries is needed. > > After all, retries are upstream oriented. for automatically review the error...

> yes, maybe some conditions I list are not reasonable. Just for this kind customized need i want to support. For users, routing is a better understanding granularity in a...

> > > I would like to know in what scenario support for route level upstream retries is needed. > > > After all, retries are upstream oriented. > >...

> What you seem to need at the moment is a retry policy that is isolated for upstreams, i.e. each upstream has its own retry policy. If multiple routes are...

> @FinerKeysen Could you give us an actual case about why we need to support the retry policy on the route level? I know that Envoy supports configuring retry policy...