[MCOL-378] Test002 (concurrent queries) leaves queries in debug.log without "End SQL Statement" Created: 2016-10-27  Updated: 2016-10-28  Resolved: 2016-10-28

Status: Closed
Project: MariaDB ColumnStore
Component/s: ExeMgr
Affects Version/s: 1.0.4
Fix Version/s: Icebox

Type: Bug Priority: Major
Reporter: David Hall (Inactive) Assignee: David Hall (Inactive)
Resolution: Not a Bug Votes: 0
Labels: None
Environment:

CentOS 6.5



 Description   

To reproduce:
run test002 by itself
mcsadmin getactiveSQLstatements
Statements will show, even though we ostensibly don't have any SQL running. getactiveSQLstatements parses debug.log to look for unmatched begin SQL statement lines. A visual inspection of debug.log shows this.

We don't yet know if the statements finished and just didn't log, or if they didn't finish properly.



 Comments   
Comment by David Hall (Inactive) [ 2016-10-28 ]

The statements finish properly and syslog is called to log the End SQL debug log line. For some reason, it never gets into the file. The probability is that the test is spewing more log lines than syslog can handle. a quote from somebody's blog:

by default syslog willl use UDP to transmit the messages, so an overloaded log server will simply result in the messages being dropped.

Sometimes we see poorly formed messages in the debug log due to partial dropping of the text.

Generated at Thu Feb 08 02:20:37 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.