Open alexandrlevashov opened 5 years ago
Hello! OK, I will try to reproduce it firstly :)
@alexandrlevashov
Have you observed any error log messages in your error.log
?
Hello!
Sorry for over a year of silence.
There is no any additional errors except "Bad file descriptor".
After some new play with this issue, I found that this error occurs if I return file:close() directly from a function that opened a file.
For instance, this will produce some times the error at close():
function test()
local file, err = ngx_io.open("name", "w+")
file:write("something to write")
return file:close()
end
But the following will not produce the error:
function test()
local file, err = ngx_io.open("name", "w+")
file:write("something to write")
local res, err = file:close()
return res, err
end
I still cannot reproduce it on demand from a test, but on high loaded server it is reproduced all the time.
Hi!
The following error occurs very often: close() failed (9: Bad file descriptor)
This is produced at the end of the complex PUT workflow (described below) after main data already written and re-sended and a small piece of data should be placed in a separate file (it is point 5 of the PUT workflow). The exact code:
The last file:close is the problem that returns the error "close() failed (9: Bad file descriptor)" .
Requesting model is the following. There are many PUT/HEAD/GET/DELETE requests at 1Gbps speed. Most PUT requests write file data locally and send it to other service using this library: https://github.com/ledgetech/lua-resty-http
so chunks are read, written to local file and forwarded to other service.
GET requests read file and "print" data to output.
Chunk size is 65536 bytes.
PUT is most interested since http request to forward data is sent to local "proxy_pass" location that passes query to an external service.
So PUT sequence is:
Input and external requests are secured with https.