recieved 4294962489-bytes data exceeding the limit 1048560 bytes

[yinhm]

I have seen a lot of this exceeding limit error after rev 4320b5b:

2015/04/10 14:35:47 transport: http2Server connection error: desc = "recieved 4294958892-bytes data exceeding the limit 1048560 bytes"

Server and client are running at the same grpc-go version. This happens when I have 1020 clients consume jobs, then streaming updates to server, request speed is about 1001000/s.

What version of Go are you using (go version)?
go version go1.4.2 linux/amd64

What operating system and processor architecture are you using?

Linux instance-1 3.16.0-30-generic #40~14.04.1-Ubuntu SMP Thu Jan 15 17:43:14 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

[dsymonds]

That number is -8404, overflowed into a uint32. It sounds like some maths went wrong somewhere along the line in the grpc-go code.

[yinhm]

@dsymonds Sounds logic.

There is no way client send that much data. Also, the counted bytes are random, eg:

2015/04/10 14:39:05 transport: http2Server connection error: desc = "recieved 4294959553-bytes data exceeding the limit 1048560 bytes"
2015/04/10 14:39:08 transport: http2Server connection error: desc = "recieved 4294955938-bytes data exceeding the limit 1048560 bytes"
2015/04/10 14:39:09 transport: http2Server connection error: desc = "recieved 4294963741-bytes data exceeding the limit 1048560 bytes"
2015/04/10 14:39:10 transport: http2Server connection error: desc = "recieved 4294964600-bytes data exceeding the limit 1048560 bytes"
2015/04/10 14:39:15 transport: http2Server connection error: desc = "recieved 4294962664-bytes data exceeding the limit 1048560 bytes"
2015/04/10 14:39:25 transport: http2Server connection error: desc = "recieved 4294957419-bytes data exceeding the limit 1048560 bytes"
2015/04/10 14:39:28 transport: http2Server connection error: desc = "recieved 4294959790-bytes data exceeding the limit 1048560 bytes"
2015/04/10 14:39:28 transport: http2Server connection error: desc = "recieved 4294960371-bytes data exceeding the limit 1048560 bytes"
2015/04/10 14:39:31 transport: http2Server connection error: desc = "recieved 4294958567-bytes data exceeding the limit 1048560 bytes"
2015/04/10 14:39:33 transport: http2Server connection error: desc = "recieved 4294965801-bytes data exceeding the limit 1048560 bytes"
2015/04/10 14:39:35 transport: http2Server connection error: desc = "recieved 4294966930-bytes data exceeding the limit 1048560 bytes"
2015/04/10 14:39:38 transport: http2Server connection error: desc = "recieved 4294959610-bytes data exceeding the limit 1048560 bytes"
2015/04/10 14:39:44 transport: http2Server connection error: desc = "recieved 4294962618-bytes data exceeding the limit 1048560 bytes"
2015/04/10 14:39:52 transport: http2Server connection error: desc = "recieved 4294960581-bytes data exceeding the limit 1048560 bytes"
2015/04/10 14:39:54 transport: http2Server connection error: desc = "recieved 4294962832-bytes data exceeding the limit 1048560 bytes"
2015/04/10 14:39:59 transport: http2Server connection error: desc = "recieved 4294966675-bytes data exceeding the limit 1048560 bytes"
2015/04/10 14:40:04 transport: http2Server connection error: desc = "recieved 4294966801-bytes data exceeding the limit 1048560 bytes"
2015/04/10 14:40:08 transport: http2Server connection error: desc = "recieved 4294965389-bytes data exceeding the limit 1048560 bytes"
2015/04/10 14:40:20 transport: http2Server connection error: desc = "recieved 4294952903-bytes data exceeding the limit 1048560 bytes"
2015/04/10 14:40:29 transport: http2Server connection error: desc = "recieved 4294956834-bytes data exceeding the limit 1048560 bytes"
2015/04/10 14:40:32 transport: http2Server connection error: desc = "recieved 4294960782-bytes data exceeding the limit 1048560 bytes"

[iamqizhao]

is there a way I can reproduce this?

[iamqizhao]

This could be fixed by #160 already. Can you sync the repo and retry? Let me know if it still sustains. In meanwhile, I will add a new end2end test case to mimic your use case next week.

[yinhm]

@iamqizhao Sorry, I may not be able to reproduce this. I encountered this issue when archiving our feed at friendfeed, https://github.com/yinhm/friendfeed

Since friendfeed was closed, I have no longer be able to reproduce. So sad.

[iamqizhao]

This should be fixed by #162. I reproduced the error you got with the existing test cases.