> *From: *Michael Fong
> *Sent: *11 октября 2018 г. 7:15
> *To: *user@ignite.apache.org
> *Subject: *Re: BufferUnderflowException on GridRedisProtocolParser
>
>
>
> Hi,
>
>
>
> The symptom seems very likely to IGNITE-7153, where the default tcp send
> buffe
октября 2018 г. 7:15
To: user@ignite.apache.org
Subject: Re: BufferUnderflowException on GridRedisProtocolParser
Hi,
The symptom seems very likely to IGNITE-7153, where the default tcp send buffer
on that environment happens to be 4096
[root]# cat /proc/sys/net/ipv4/tcp_wmem
4096
Regards
Hi,
The symptom seems very likely to IGNITE-7153, where the default tcp send
buffer on that environment happens to be 4096
[root]# cat /proc/sys/net/ipv4/tcp_wmem
4096
Regards,
On Thu, Oct 11, 2018 at 10:56 AM Michael Fong wrote:
> Hi,
>
> Thank you for your response. Not to every request; we
Hi,
Thank you for your response. Not to every request; we only see this for
some specific ones - when elCnt (4270) > buf.limit (4096). We are trying
to narrowing down the data set to find the root cause.
Thanks.
Regards,
On Thu, Oct 11, 2018 at 12:08 AM Ilya Kasnacheev
wrote:
> Hello!
>
>
Hello!
Do you see this error on every request, or on some specific ones?
Regards,
--
Ilya Kasnacheev
вт, 9 окт. 2018 г. в 15:54, Michael Fong :
> Hi, all
>
> We are evaluating Ignite compatibility with Redis protocol, and we hit an
> issue as the following:
> Does the stacktrace look a bit
It definitely does.
IGNITE-7153 seems to be applicable for objects greater than 8 kb. Is that your
case?
If so then I guess that has to be the same issue.
Stan
From: Michael Fong
Sent: 9 октября 2018 г. 15:54
To: user@ignite.apache.org
Subject: BufferUnderflowException
Hi, all
We are evaluating Ignite compatibility with Redis protocol, and we hit an
issue as the following:
Does the stacktrace look a bit like IGNITE-7153?
java.nio.BufferUnderflowException
at java.nio.HeapByteBuffer.get(HeapByteBuffer.java:151)
at
