[MCOL-1323] cpimport Splitter has incorrect SIGPIPE mapping Created: 2018-04-04 Updated: 2020-08-25 Resolved: 2018-04-17 |
|
| Status: | Closed |
| Project: | MariaDB ColumnStore |
| Component/s: | cpimport |
| Affects Version/s: | 1.0.12 |
| Fix Version/s: | 1.1.4 |
| Type: | Bug | Priority: | Major |
| Reporter: | David Hall (Inactive) | Assignee: | Daniel Lee (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Sprint: | 2018-07, 2018-08 |
| Description |
|
WESplitterApp::setupSignalHandlers() has an incorrect mapping of SIGPIPE to the SIGHUP handler. SIGPIPE is intended to be ignored and SIGHUP causes an immediate kill. The incorrect mapping causes SIGPIPE to incorrectly kill the process. |
| Comments |
| Comment by David Hall (Inactive) [ 2018-04-04 ] |
|
This problem only arises if the UM is under extreme load and is slow to process the EOD responses. The PM's cpimport might have already closed the socket, causing a SIGPIPE that should be ignored. By killing the process, the table lock is left on, which causes some consternation. Test: I'm not sure how to force the UM to slow to the point this becomes an issue. Obviously a customer has succeeded in doing so. |
| Comment by Daniel Lee (Inactive) [ 2018-04-17 ] |
|
Build verified: 1.1.4-1 source /root/columnstore/mariadb-columnstore-server Merge pull request #110 from mariadb-corporation/ /root/columnstore/mariadb-columnstore-server/mariadb-columnstore-engine Merge pull request #447 from mariadb-corporation/ Using the following steps: 1. start cpimport for 10g lineitem Reproduced the issue in 1.0.12-1. Cpimport aborted and left the lineitem tabled locked. In 1.1.4-1, cpimport did not abort and kept going and finished. |