Alexey Serbin created KUDU-3456:
-----------------------------------
Summary: 'kudu table copy' CLI crashes on write failures not
outputting useful information on errors
Key: KUDU-3456
URL: https://issues.apache.org/jira/browse/KUDU-3456
Project: Kudu
Issue Type: Bug
Components: CLI
Affects Versions: 1.16.0, 1.15.0, 1.14.0, 1.13.0, 1.11.1, 1.12.0, 1.11.0,
1.10.1, 1.10.0
Reporter: Alexey Serbin
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.
{noformat}
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)
{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
