Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
6.2.2
-
None
-
2021-16
Description
A simple connect to the DDLProc port can render the process useless:
curl -v telnet://cs1:8612
|
Which causes this error:
root@cs1:/tmp$ mysql -s
|
MariaDB [(none)]> create table inventory.t(col1 varchar(100)) engine=columnstore;
|
ERROR 1815 (HY000): Internal error: Lost connection to DDLProc
|
MariaDB [(none)]>
|
For more details, and reason this can be important for all customers, please refer to CS0346013.
Attachments
Activity
Build verified: 6.2.3-1 (#3561)
Reproduced the reported issues in 6.2.2
After telnet made the connection, DDL would failed as reported. It would continue to fail, even after telnet connection has been terminated
With the new build, DDL would wait while the telnet connection is live. After telnet connection has been terminated, DDL would work.
4QA The patch changes the way we read data from socket. Previously DMLProc thread synchronously wait for some data to appear in the socket and this read call can last forever. Now DMLProc logs an error, closes the socket and proceeds.