[
https://issues.apache.org/jira/browse/IGNITE-20897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maksim Timonin updated IGNITE-20897:
------------------------------------
Ignite Flags: (was: Docs Required,Release Notes Required)
> Ignite should clean tmp binaryMeta files on start
> -------------------------------------------------
>
> Key: IGNITE-20897
> URL: https://issues.apache.org/jira/browse/IGNITE-20897
> Project: Ignite
> Issue Type: Bug
> Reporter: Maksim Timonin
> Priority: Major
>
> Ignite uses tmp files for BinaryMeta for creation. It's possible to land with
> the tmp file after Ignite node failed. Then such a file must be remove on
> Ignite start.
> The problem is to find a place where to clean these files:
> # BinaryMetadataAsyncWriter is a thread that actually writes to binary meta.
> # But this thread is also created by StandaloneGridKernalContext instances
> on start. It means that utils using it might have write access to the
> binary_meta directory.
> Options are:
> # Clean files in any callback after Ignite started (#onKernalStart0)
> # Make BinaryMetadataFileStore read only for utils.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
