[
https://issues.apache.org/jira/browse/KUDU-934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adar Dembo resolved KUDU-934.
-----------------------------
Resolution: Duplicate
Fix Version/s: n/a
Target Version/s: M5 (was: 1.8.0)
This got fixed back in September of 2016, and was tracked in KUDU-668.
> Crash between creating log metadata and log container prevents restart
> ----------------------------------------------------------------------
>
> Key: KUDU-934
> URL: https://issues.apache.org/jira/browse/KUDU-934
> Project: Kudu
> Issue Type: Bug
> Components: fs
> Affects Versions: Private Beta
> Reporter: Todd Lipcon
> Priority: Major
> Fix For: n/a
>
>
> If the TS crashes after making a log metadata file, but before making the
> associated data file, then it will fail to restart with a message like:
> I0804 11:39:24.298252 50360 server_base.cc:139] Could not load existing FS
> layout: Not found: Could not open container e29e2bd193374c85b026a48314d22069:
> /tmp/kudutest-4100/alter_table-randomized-test.AlterTableRandomized.TestRandomSequence.1438713552754543-46329/minicluster-data/ts-0/data/e29e2bd193374c85b026a48314d22069.data:
> No such file or directory (error 2)
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
