You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vadim Pakhnushev (Jira)" <ji...@apache.org> on 2026/01/23 09:38:00 UTC

[jira] [Assigned] (IGNITE-27539) Unit deployment hangs on case-insentivite fs

     [ https://issues.apache.org/jira/browse/IGNITE-27539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vadim Pakhnushev reassigned IGNITE-27539:
-----------------------------------------

    Assignee: Vadim Pakhnushev

> Unit deployment hangs on case-insentivite fs
> --------------------------------------------
>
>                 Key: IGNITE-27539
>                 URL: https://issues.apache.org/jira/browse/IGNITE-27539
>             Project: Ignite
>          Issue Type: Bug
>          Components: code deployment ai3
>            Reporter: Vadim Pakhnushev
>            Assignee: Vadim Pakhnushev
>            Priority: Major
>              Labels: ignite-3
>
> When deploying files with names that are equals ignoring case on a node running on a case-insentitive files system, deployment doesn't complete with this rather cryptic exception in the node's log:
> {noformat}
> [DeployerProcessor] Failed to process deploy action.
> java.nio.file.NoSuchFileException: ...deployment.tmp\unitId\1.1.1\SMALL.TXT -> deployment\unitId\1.1.1\SMALL.TXT
> {noformat}
> This happens because we write both input files to the same underlying file on the FS.
> Then during deployment we move them from the temporary storage to the deployment location and second move fails because the file was already moved out.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)