E> ER_INVALID_MSGPACK: Invalid MsgPack - packet body
2019-07-01 14:43:34.694 [1] iproto iproto.cc:554 W> stopping input on connection fd 19, aka 192.168.57.49:3301, peer of 192.168.88.136:45660, readahead limit is reached
2019-07-01 14:43:35.200 [1] iproto xrow.c:207 E> ER_INVALID_MSGPACK: Invalid MsgPack - packet body
2019-07-01 14:43:35.383 [1] iproto iproto.cc:566 W> 129 messages suppressed
2019-07-01 14:43:35.384 [1] iproto iproto.cc:566 W> stopping input on connection fd 19, aka 192.168.57.49:3301, peer of 192.168.88.136:45660, net_msg_max limit is reached
2019-07-01 14:43:35.428 [1] iproto/101/main iproto.cc:566 W> stopping input on connection fd 19, aka 192.168.57.49:3301, peer of 192.168.88.136:45660, net_msg_max limit is reached
2019-07-01 14:43:35.429 [1] iproto/101/main iproto.cc:566 W> stopping input on connection fd 19, aka 192.168.57.49:3301, peer of 192.168.88.136:45660, net_msg_max limit is reached
2019-07-01 14:43:35.429 [1] iproto/101/main iproto.cc:566 W> stopping input on connection fd 19, aka 192.168.57.49:3301, peer of 192.168.88.136:45660, net_msg_max limit is reached
2019-07-01 14:43:35.429 [1] iproto/101/main iproto.cc:566 W> stopping input on connection fd 19, aka 192.168.57.49:3301, peer of 192.168.88.136:45660, net_msg_max limit is reached
2019-07-01 14:43:35.429 [1] iproto/101/main iproto.cc:566 W> stopping input on connection fd 19, aka 192.168.57.49:3301, peer of 192.168.88.136:45660, net_msg_max limit is reached
2019-07-01 14:43:35.429 [1] iproto/101/main iproto.cc:566 W> stopping input on connection fd 19, aka 192.168.57.49:3301, peer of 192.168.88.136:45660, net_msg_max limit is reached
2019-07-01 14:43:35.429 [1] iproto/101/main iproto.cc:566 W> stopping input on connection fd 19, aka 192.168.57.49:3301, peer of 192.168.88.136:45660, net_msg_max limit is reached
2019-07-01 14:43:35.429 [1] iproto/101/main iproto.cc:566 W> stopping input on connection fd 19, aka 192.168.57.49:3301, peer of 192.168.88.136:45660, net_msg_max limit is reached
2019-07-01 14:43:35.429 [1] iproto/101/main iproto.cc:566 W> stopping input on connection fd 19, aka 192.168.57.49:3301, peer of 192.168.88.136:45660, net_msg_max limit is reached
2019-07-01 14:43:35.688 [1] iproto xrow.c:207 E> ER_INVALID_MSGPACK: Invalid MsgPack - packet body
2019-07-01 14:43:35.984 [1] iproto xrow.c:207 E> ER_INVALID_MSGPACK: Invalid MsgPack - packet body
2019-07-01 14:43:36.098 [1] iproto xrow.c:207 E> ER_INVALID_MSGPACK: Invalid MsgPack - packet body
2019-07-01 14:43:36.198 [1] iproto xrow.c:207 E> ER_INVALID_MSGPACK: Invalid MsgPack - packet body
2019-07-01 14:43:36.391 [1] iproto xrow.c:207 E> ER_INVALID_MSGPACK: Invalid MsgPack - packet body
2019-07-01 14:43:36.497 [1] iproto xrow.c:207 E> ER_INVALID_MSGPACK: Invalid MsgPack - packet body
2019-07-01 14:43:36.785 [1] iproto xrow.c:207 E> ER_INVALID_MSGPACK: Invalid MsgPack - packet body
2019-07-01 14:43:36.987 [1] iproto xrow.c:207 E> ER_INVALID_MSGPACK: Invalid MsgPack - packet body
2019-07-01 14:43:37.108 [1] iproto xrow.c:207 E> ER_INVALID_MSGPACK: Invalid MsgPack - packet body
Портянка больше, чем могла бы быть, но тут суть в том, что количественно сообщения
iproto/101/main iproto.cc:566 W> stopping input
совпадают с
iproto xrow.c:207 E> ER_INVALID_MSGPACK
Если net_msg_max ограничивает количество файберов, то почему запросы разваливаются?
@sergepetrenko Тебе знакомо?
а точно клиенты нормальные пакеты шлют?
Обсуждают сегодня