bug: key not found

[a11enhuang]

系统中有大量的Key Not found日志，并且配置的plugin有概率不生效

2021-11-24T03:39:38.240Z WARN server/server.go:59 key not found
2021/11/24 上午11:39:38 , context: ngx.timer
2021/11/24 上午11:39:38 2021/11/24 03:39:38 [warn] 58#58: *203 [lua] init.lua:681: 2021-11-24T03:39:38.247Z INFO server/server.go:105 Client connected (unix)
2021/11/24 上午11:39:38 , context: ngx.timer
2021/11/24 上午11:39:38 2021/11/24 03:39:38 [warn] 58#58: *203 [lua] init.lua:681: 2021-11-24T03:39:38.247Z INFO server/server.go:121 receive rpc type: 2 data length: 1920
2021/11/24 上午11:39:38 , context: ngx.timer
2021/11/24 上午11:39:38 2021/11/24 03:39:38 [warn] 58#58: *203 [lua] init.lua:681: 2021-11-24T03:39:38.248Z WARN server/server.go:59 key not found
2021/11/24 上午11:39:38 , context: ngx.timer
2021/11/24 上午11:39:38 2021/11/24 03:39:38 [warn] 58#58: *203 [lua] init.lua:681: 2021-11-24T03:39:38.251Z INFO server/server.go:121 receive rpc type: 2 data length: 1924
2021/11/24 上午11:39:38 , context: ngx.timer
2021/11/24 上午11:39:38 2021/11/24 03:39:38 [warn] 58#58: *203 [lua] init.lua:681: 2021-11-24T03:39:38.251Z WARN server/server.go:59 key not found
2021/11/24 上午11:39:38 , context: ngx.timer
2021/11/24 上午11:39:38 2021/11/24 03:39:38 [warn] 58#58: *203 [lua] init.lua:681: 2021-11-24T03:39:38.295Z INFO server/server.go:121 receive rpc type: 2 data length: 1916
2021/11/24 上午11:39:38 , context: ngx.timer
2021/11/24 上午11:39:38 2021/11/24 03:39:38 [warn] 58#58: *203 [lua] init.lua:681: 2021-11-24T03:39:38.296Z WARN server/server.go:59 key not found
2021/11/24 上午11:39:38 , context: ngx.timer
2021/11/24 上午11:39:38 2021/11/24 03:39:38 [warn] 58#58: *203 [lua] init.lua:681: 2021-11-24T03:39:38.317Z INFO server/server.go:121 receive rpc type: 2 data length: 1916
2021/11/24 上午11:39:38 2021-11-24T03:39:38.317Z WARN server/server.go:59 key not found
2021/11/24 上午11:39:38 , context: ngx.timer

[spacewander]

Duplicate of #43

[a11enhuang]

如果是key not found的情况下，不会走过滤器。如果我重新部署APISIX，一切又恢复了正常

[goxiaoy]

Confirm happens with following steps:

• Start APISIX with docker image and set ext-plugin.path_for_test
• Start plugin runner
• Make some requests. works fine.
• Terminate plugin runner
• Make some requests.
• Restart plugin runner, make some requests. Run into this issue
• Restart APISIX, works fine

[spacewander]

@goxiaoy
It's fine. See https://github.com/apache/apisix-go-plugin-runner/blob/master/docs/en/latest/getting-started.md

If you see refresh cache and try again warning on APISIX side and key not found warning on Runner side during development, this is due to configuration cache inconsistency. Because the Runner is not managed by APISIX in the development state, the internal state may be inconsistent. Don't worry, APISIX will retry.

[spacewander]

Closed as lack of response from the author. Feel free to reopen it if need.