[MCOL-49] Drop table error Created: 2016-05-09 Updated: 2016-09-15 Resolved: 2016-09-15 |
|
| Status: | Closed |
| Project: | MariaDB ColumnStore |
| Component/s: | DDLProc |
| Affects Version/s: | None |
| Fix Version/s: | 1.0.2, 1.0.3 |
| Type: | Bug | Priority: | Major |
| Reporter: | Daniel Lee (Inactive) | Assignee: | Daniel Lee (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Environment: |
1 UM and 2 PMs |
||
| Issue Links: |
|
||||||||
| Description |
|
The stack 1um-2PM stack ran out of disk space during a regression test and I could not drop tables. I manually tried to drop tables (not part of this regression test) and also got the error. I also created a single-column table and tried to drop it and also got the same error. UM1 error.log: MariaDB [tpch100c]> drop table nation; pm1 error.log May 9 09:55:43 s1pm1 PrimProc[7154]: 43.846635 |0|0|0| C 28 CAL0000: columncommand.cpp error on projectResultRG for oid 1041 lbid 222208: input rids 290, output rids 287#012: Restarted a syscat job 120 times, bailing#012 I eventually had to do a new installation (both RPMs and empty databases). With more disk space available, the regression test was able to run. |
| Comments |
| Comment by Dipti Joshi (Inactive) [ 2016-05-31 ] |
|
dleeyh Did the UM run out of disk space or PM ? |
| Comment by Dipti Joshi (Inactive) [ 2016-08-02 ] |
|
dleeyh Is this still happening with latest build ? |
| Comment by David Hall (Inactive) [ 2016-08-18 ] |
|
I believe this is fixed by another MCOL |
| Comment by Dipti Joshi (Inactive) [ 2016-08-30 ] |
|
dleeyh Please test this against 1.0.2 and close it if it has ben resolved. |
| Comment by Daniel Lee (Inactive) [ 2016-09-15 ] |
|
This is no longer an issue in 1.0.2 and 1.0.3 |