Abhishek Chennaka created KUDU-3534: ---------------------------------------
Summary: Corrupt timestamps crash the server Key: KUDU-3534 URL: https://issues.apache.org/jira/browse/KUDU-3534 Project: Kudu Issue Type: Improvement Reporter: Abhishek Chennaka Cam across a situation where the tablet server was crashing with the below log messages: I1204 03:42:13.302340 124627 maintenance_manager.cc:382] P 035c5ff8ec2f4f71878f96adb9632c3c: Scheduling CompactRowSetsOp(886eddb2ccca466995e400c62c1b1197): perf score=0.561641 .. F1204 03:42:20.046682 124484 compaction.cc:465] Check failed: 0 != ret (0 vs. 0) The reason behind is that there were two separate delete ops with the same exact hybrid stamp which is not ideally possible. This was noticed across multiple replicas in the same server so most likely it is a server specific issue (probably disk related) while the same replicas in other servers did not thrown an issue. -- This message was sent by Atlassian Jira (v8.20.10#820010)