v.19.3New Features

Added the KILL MUTATION Statement That Allows Removing Mutations That Are for Some Reasons Stuck

Added the KILL MUTATION statement that allows removing mutations that are for some reasons stuck. Added latest_failed_part, latest_fail_time, latest_fail_reason fields to the system.mutations table for easier troubleshooting. #4287 (Alex Zatelepin)
Added the KILL MUTATION statement to remove stuck mutations and enhanced the system.mutations table with latest_failed_part, latest_fail_time, and latest_fail_reason fields for better mutation troubleshooting.

Why it matters

This feature addresses the issue of mutations getting stuck and provides administrators with tools to manually terminate these stuck mutations. Additionally, the new fields in the system.mutations table help users identify and diagnose mutation failures more effectively by providing detailed failure information.

How to use it

To remove a stuck mutation, use the KILL MUTATION statement targeting the specific mutation. For troubleshooting, query the system.mutations table and utilize the new fields (latest_failed_part, latest_fail_time, latest_fail_reason) to gather information about the most recent mutation failures.