You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Alexey Goncharuk (Jira)" <ji...@apache.org> on 2019/09/09 15:33:00 UTC
[jira] [Assigned] (IGNITE-12106) Rework ignite binary metadata
exception for ease of troubleshooting
[ https://issues.apache.org/jira/browse/IGNITE-12106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexey Goncharuk reassigned IGNITE-12106:
-----------------------------------------
Assignee: Alexey Goncharuk
> Rework ignite binary metadata exception for ease of troubleshooting
> -------------------------------------------------------------------
>
> Key: IGNITE-12106
> URL: https://issues.apache.org/jira/browse/IGNITE-12106
> Project: Ignite
> Issue Type: Bug
> Components: cache, persistence
> Affects Versions: 2.7.5, 2.7.6
> Reporter: Denis Magda
> Assignee: Alexey Goncharuk
> Priority: Blocker
> Fix For: 2.7.6
>
>
> An exception of this kind happens regularly and its message doesn't suggest why it took place and how to fix the issue:
> {noformat}
> Cannot find metadata for object with compact footer: 2097659979
> {noformat}
> See this thread for more details:
> http://apache-ignite-developers.2346864.n4.nabble.com/Metastore-disappears-in-Docker-on-restarts-td43107.html
> As a solution, let's rework this exception to ensure that the way like that "Ignite work directory might be cleared on restarts. Ensure that IGNITE_HOME doesn't point to a temp folder or any other folder that is destroyed/erased on restarts. Presently, IGNITE_HOME points to..."
--
This message was sent by Atlassian Jira
(v8.3.2#803003)