For some reasons when we delete a MergeTree Part in atomic way something may go wrong - and leave the `delete_tmp_*` folder or it's part on disk. This may lead to a disk space consumption over time.

It's suggested to delete this folders at least at server start-up. Current solution with `clearOldTemporaryDirectories()` doesn't work because this method is called periodically from a thread without any locks or advisory on folders - it may cause the race conditions.
{
    NameSet part_names_successeded;
    auto get_failed_parts = [&part_names_successeded, &parts_failed_to_delete, &parts] ()
    {
        if (part_names_successeded.size() == parts.size())
            return;
        if (parts_failed_to_delete)
        {
            for (const auto & part : parts)
            {
                if (!part_names_successeded.contains(part->name))
                    parts_failed_to_delete->insert(part->name);
            }
        }
    };
    try
    {
        clearPartsFromFilesystemImpl(parts, &part_names_successeded);
        get_failed_parts();
    }
    catch (...)
    {
        get_failed_parts();
        if (throw_on_error)
            throw;
    }
}
void MergeTreeData::clearPartsFromFilesystemImpl(const DataPartsVector & parts_to_remove, NameSet * part_names_successed)