go plugin excute time >= 60s will cause error (event callback failed; source=plugin_server, event=reset_instances)

[xyandy]

Is there an existing issue for this?

• I have searched the existing issues

Kong version ($ kong version)

kong:3.5

Current Behavior

i write a golang plugin. It sleep xxx seconds and then return response. codes are below:

package main

import (
	"fmt"
	"net/http"
	"time"

	"github.com/Kong/go-pdk"
	"github.com/Kong/go-pdk/server"
)

func main() {
	var version = "0.1"
	var priority = 100
	server.StartServer(New, version, priority)
}

type Config struct {
	Timeout int `json:"timeout"`
}

func New() interface{} {
	return &Config{
		Timeout: 10,
	}
}

func (conf Config) Access(kong *pdk.PDK) {
	method, _ := kong.Request.GetMethod()
	path, _ := kong.Request.GetPath()
	bodyBytes, _ := kong.Request.GetRawBody()
	str := fmt.Sprintf("method: %s, path: %s, body: %s", method, path, string(bodyBytes))

	kong.Log.Notice(str)
	time.Sleep(time.Duration(conf.Timeout) * time.Second)
	kong.Response.Exit(http.StatusOK, []byte(str), nil)
}

If the timeout >= 60s, it will return the below error:

Expected Behavior

Can we provide a argument that could set up the plugin event callback timeout ?

Steps To Reproduce

No response

Anything else?

No response

[git-hulk]

This bug seems to have been resolved by #11819.

[xyandy]

This bug seems to have been resolved by #11819.

This PR is merged on Nov 7, 2023. But kong 3.5 is released on Nov 8, 2023...
Looks like Kong 3.5 contains this pr changes? But it doesn't work ?

[git-hulk]

@xyandy I believe you can check this by taking a look at the commit history of 3.5.0 instead of by date only.

This PR commit was first released in 3.6.0:

[StarlightIbuki]

Please try with 3.6 to see if the issue persists.

[xyandy]

I tried kong:3.7. It works and will not report the error (event callback failed; source=plugin_server, event=reset_instances)

But can we just increment the timeout that nginx lua call go plugin server?

Let's assume a scenario:

We wanna call a backend api to check if the request Authorization header is valid in plugin Access(pdk) function.
The backend api is slow and it spends about 61s.

We think it is ok. But now, it will report [plugin] timeout...

[StarlightIbuki]

Actually, it's possible: lua_socket_connect_timeout can be used.

[xyandy]

I deploy kong:3.7 in k8s.. add container env: KONG_NGINX_HTTP_LUA_SOCKET_CONNECT_TIMEOUT=80

But it seems that it doesn't work... after 60s, it logs [plugin] timeout

[xyandy]

OK, just set lua_socket_read_timeout solves this problem