[KUDU-3456] 'kudu table copy' CLI crashes on write failures not outputting useful information on errors

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.10.0, 1.10.1, 1.11.0, 1.12.0, 1.11.1, 1.13.0, 1.14.0, 1.15.0, 1.16.0
• Fix Version/s: 1.17.0
• Component/s: CLI
• Assignee: Alexey Serbin
• Reporter: Alexey Serbin
• Created: 06/Mar/23 21:18
• Updated: 06/Mar/23 21:21
• Resolved: 06/Mar/23 21:21

Description

On write errors (say, a duplicate primary key because a row already exists), the kudu tablet copy CLI tools crashing with the stack trace similar to the snippet below. There isn't any information output on the actual per-row errors into the log, and that complicates troubleshooting.

F0228 17:52:31.438441 97571 table_scanner.cc:529] Check failed: _s.ok() Bad status: IO error: Some errors occurred
*** Check failure stack trace: ***
    @          0x140e48d  google::LogMessage::Fail()
    @          0x141009e  google::LogMessage::SendToLog()
    @          0x140e010  google::LogMessage::Flush()
    @          0x1410989  google::LogMessageFatal::~LogMessageFatal()
...
    @          0x145a7ff  kudu::tools::TableScanner::ScanData()
    @          0x145af69  kudu::tools::TableScanner::CopyTask()
...
Aborted (core dumped)