sanikolaev
commented
1 month ago Thanks @kashak88
MRE
mysql> drop table if exists t; create table t(a int, b int, c int, d int, e int, f int); insert into t(id) values(1); drop table if exists d; create table d type='distributed' agent='127.0.0.1:9312:t'; select id from d group by a order by a desc, b desc, c desc, d desc, e desc, f desc facet a;
--------------
drop table if exists t
--------------
Query OK, 0 rows affected (0.01 sec)
--------------
create table t(a int, b int, c int, d int, e int, f int)
--------------
Query OK, 0 rows affected (0.00 sec)
--------------
insert into t(id) values(1)
--------------
Query OK, 1 row affected (0.00 sec)
--------------
drop table if exists d
--------------
Query OK, 0 rows affected (0.00 sec)
--------------
create table d type='distributed' agent='127.0.0.1:9312:t'
--------------
Query OK, 0 rows affected (0.00 sec)
--------------
select id from d group by a order by a desc, b desc, c desc, d desc, e desc, f desc facet a
--------------
ERROR 2013 (HY000): Lost connection to MySQL server during query
No connection. Trying to reconnect...
ERROR 2003 (HY000): Can't connect to MySQL server on '0:9306' (61)
ERROR:
Can't connect to the serverNotes:
FACETis importantgroup byis important- the excessive ordering is important
Bug Description:
Hi, It seems like a query that exceeds sort-by attributes limit of 5 is allowed to be sent to cluster nodes from master and doing so crashes those nodes, for example: When I run the query directly on the cluster node:
When I run it on master and it's forwarded to the node above:
Crash log from grs-uat-manticore1:
I image that this can be replicated on your side without our indices. Master config is pretty simple:
Manticore Search Version:
6.3.0
Operating System Version:
ubuntu 20.04
Have you tried the latest development version?
Internal Checklist:
To be completed by the assignee. Check off tasks that have been completed or are not applicable.