Skip to content

bug: http service should not be started before etcd data is pulled #3370

Description

@hizzd

Issue description

that when accessing immediately after apisix is started, it will return:

{"error_msg ": "404 Route Not Found"}

Is it because apisix did not pull the route data in etcd in time?
maybe the http service of apisix should be started after pulling etcd data.

Environment

  • apisix version: [docker] apache/apisix:2.2-alpine
  • OS: [docker] apache/apisix:2.2-alpine
  • OpenResty / Nginx version: [docker] apache/apisix:2.2-alpine
  • etcd enabled auto-tls.
  • apisix disable etcd.tls.verify.

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions