[
https://issues.apache.org/jira/browse/KUDU-1186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16104392#comment-16104392
]
Gabriel Wang edited comment on KUDU-1186 at 7/28/17 3:29 AM:
-------------------------------------------------------------
The work around is removing related folders:
e.g.
rm -rf /data/1/kudu-master
rm -rf /data/2/kudu-master
rm -rf /var/lib/kudu/master
and then restart kudu service from Cloudera manager.
was (Author: eheewag):
The work around is removing related folders:
e.g.
rm -rf /data/1/kudu-master
rm -rf /data/2/kudu-master
rm -rf /var/lib/kudu/master
> master fails to start if unable to find metadata files
> ------------------------------------------------------
>
> Key: KUDU-1186
> URL: https://issues.apache.org/jira/browse/KUDU-1186
> Project: Kudu
> Issue Type: Bug
> Components: master
> Reporter: Dan Burkert
>
> The master will refuse to start if it finds the metadata directory, but no
> files within it. This can happen if a previous startup attempt has failed
> due to clocks not being synchronized. Relevant log message:
> {code}
> Bad status: Not found: Unable to initialize catalog manager: Failed to
> initialize sys tables async: Could not load tablet metadata from
> /var/lib/kudu/master/tablet-meta/00000000000000000000000000000000:
> /var/lib/kudu/master/tablet-meta/00000000000000000000000000000000: No such
> file or directory (error 2)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
