[MCOL-480] warning error reported after upgrade to 1.0.6 Created: 2016-12-21 Updated: 2017-03-23 Resolved: 2017-03-23 |
|
| Status: | Closed |
| Project: | MariaDB ColumnStore |
| Component/s: | None |
| Affects Version/s: | 1.0.6 |
| Fix Version/s: | 1.1.0 |
| Type: | Bug | Priority: | Minor |
| Reporter: | David Hill (Inactive) | Assignee: | Daniel Lee (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||
| Sprint: | 2017-3, 2017-4, 2017-5, 2017-6 | ||||||||
| Description |
|
Upgraded a user from 1.0.4 to 1.0.6 and the below warning was issue a couple of times during the startup process and issue while they were doing queries Dec 21 09:08:16 usfit-scdb1 messagequeue[4730]: 16.942035 |0|0|0| W 31 CAL0071: InetStreamSocket::read: EOF during readToMagic: socket read error: Success; InetStreamSocket: sd: 11 inet: 192.168.212.31 port: 8630; Will retry. |
| Comments |
| Comment by David Hill (Inactive) [ 2017-01-20 ] |
|
update, still happening in 1.0.7... of course Jan 20 15:47:39 ip-10-87-5-72 messagequeue[5898]: 39.141524 |0|0|0| W 31 CAL0071: InetStreamSocket::read: EOF during readToMagic: socket read error: Success; InetStreamSocket: sd: 11 inet: 10.87.5.72 port: 8630; Will retry. |
| Comment by David Hall (Inactive) [ 2017-02-06 ] |
|
Originally, code inspection would lead one to think this code path was abnormal. It is not and no warning should be emitted. The warning is now suppressed. |
| Comment by Ben Thompson (Inactive) [ 2017-02-21 ] |
|
Reviewed and Merged |
| Comment by Daniel Lee (Inactive) [ 2017-03-22 ] |
|
I reproduced the reported issue when upgrading from 1.0.4-1 to 1.0.6-1. After chatted with developer, we decided that it needs further investigation as the issue has observed since the fix. My understand is that the messages were outputted incorrectly. The developer should provide a brief explanation on the situation so that others, myself included, would not think we are just suppressing the messages and the root cause of the issue was not fixed. |
| Comment by Daniel Lee (Inactive) [ 2017-03-22 ] |
|
Build tested: 1.1.0 GitHub source Have not seen the reported messages in a new installation. The bug description talks about an upgrade. I don't know if it is an issue with the upgrade process. I will retest when the ticket is ready for QA again. |
| Comment by Daniel Lee (Inactive) [ 2017-03-23 ] |
|
New installation of 1.0.6-1 also had the same issue. The issue was not related to the upgrade process. Closed per my test result in the last messages. |