-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
error logs: NC_ request #672
Comments
The request is incomplete. the client closing the connection caused the eof (end-of-file) to be syslogged ( The fact that the length was exactly 4096 may or may not be related - the client might have if (conn->eof) {
msg = conn->rmsg;
/* client sent eof before sending the entire request */
if (msg != NULL) {
conn->rmsg = NULL;
ASSERT(msg->peer == NULL);
ASSERT(msg->request && !msg->done);
log_error("eof c %d discarding incomplete req %"PRIu64" len "
"%"PRIu32"", conn->sd, msg->id, msg->mlen);
req_put(msg);
} |
Programming language of this application is golang, we use an open lib on github for connecting to twemproxy, and the backend is memcached. the open lib like is : "github.com/bradfitz/gomemcache/memcache" |
Hello, twemprodxy reported some error logs: NC_ request. c: 417 EOF C 249 discarding incomplete req 33270941169 len 4096, but I didn't understand what the error was, and then the error was reported. At the same time, the connection timeout occurred in the program at the same time, and the error occurred in the twoproxy at the same time_ The connection also fluctuates, so I want to find out where the problem is with the twoproxy.
The text was updated successfully, but these errors were encountered: