[MCOL-121] MySQL client reports "stage 2 - enabling keys" for every query against a CS table. Created: 2016-06-11 Updated: 2016-11-23 Resolved: 2016-11-23 |
|
| Status: | Closed |
| Project: | MariaDB ColumnStore |
| Component/s: | MariaDB Server |
| Affects Version/s: | None |
| Fix Version/s: | 1.0.5 |
| Type: | Bug | Priority: | Major |
| Reporter: | Justin Swanhart (Inactive) | Assignee: | Daniel Lee (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Sprint: | 2016-21, 2016-22, 2016-23 |
| Description |
|
1) 2) |
| Comments |
| Comment by David Thompson (Inactive) [ 2016-10-07 ] |
|
This is no longer happening. |
| Comment by David Thompson (Inactive) [ 2016-10-12 ] |
|
Hmmn, now i am seeing this with the current build, not sure what is the difference with when it was not happening before. |
| Comment by David Thompson (Inactive) [ 2016-10-12 ] |
|
'select * from lineitem limit 10' seems to be a good query to reproduce this consistently on. its possible that other queries are actually showing this but the query is too fast for this to be observed. |
| Comment by David Hall (Inactive) [ 2016-10-13 ] |
|
I've seen this consistently on all queries since we started the port. |
| Comment by Justin Swanhart (Inactive) [ 2016-10-16 ] |
|
Look at how the ARIA temporary table is created and populated. The message comes when the ARIA table is accessed with SELECT. |
| Comment by David Hall (Inactive) [ 2016-10-17 ] |
|
Thanks, Justin |
| Comment by David Hall (Inactive) [ 2016-10-24 ] |
|
These annoying (if they are annoying) messages can be disable by adding |
| Comment by David Hall (Inactive) [ 2016-10-24 ] |
|
Changed the default my.cnf to disable progress reporting: |
| Comment by Justin Swanhart (Inactive) [ 2016-10-24 ] |
|
then progress reporting doesn't work for operations like loading tables.. this isn't a fix IMO. |
| Comment by Daniel Lee (Inactive) [ 2016-10-27 ] |
|
Agree that we should not disable the process reporting functionality to suppress the reported issue. |
| Comment by Daniel Lee (Inactive) [ 2016-10-27 ] |
|
Per my last comment |
| Comment by David Hall (Inactive) [ 2016-10-27 ] |
|
Re-opening to look for a different answer. Allegedly, these messages aren't supposed to start until after a 5 second delay. That 5 seconds doesn't appear to be in play here. I'll hunt around. |
| Comment by David Hall (Inactive) [ 2016-10-31 ] |
|
Reversed the disabling of client status reports |
| Comment by David Hall (Inactive) [ 2016-10-31 ] |
|
I reversed my earlier suppression of the client status report. Added code to stop client status reports in copy_data_between_tables only for INFINIDB_ALTER_VTABLE, which is where the annoying messages are coming from. |
| Comment by David Hall (Inactive) [ 2016-10-31 ] |
|
For some reason, the pull request for reversing the earlier change doesn't show in the pull request list of the MCOL. Need to manually hunt it up to merge it. |
| Comment by Andrew Hutchings (Inactive) [ 2016-10-31 ] |
|
Patch looks good. Merged. Need to work some Jira magic... |
| Comment by Andrew Hutchings (Inactive) [ 2016-10-31 ] |
|
Reopening to add to sprint before putting it into testing |
| Comment by Daniel Lee (Inactive) [ 2016-11-22 ] |
|
Build tested: 1.0.5-1 mcsadmin> getsoft Name : mariadb-columnstore-platform The "enabling keys" msg is still being outputted when selecting Columnstore tables. |
| Comment by Daniel Lee (Inactive) [ 2016-11-23 ] |
|
Build verified: 1.0.5-1 mcsadmin> getsoft Name : mariadb-columnstore-platform It turned out to be a build issue. This ticket passed with the latest build. |