[
https://issues.apache.org/jira/browse/KUDU-1660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15533136#comment-15533136
]
Mike Percy commented on KUDU-1660:
----------------------------------
I tried Kudu on CentOS 6.5 and it seems to work; at least it starts up.
[~jdcryans] suggested that you may be hitting the bug fixed in
https://gerrit.cloudera.org/#/c/4535/ ... do the VMs only have a single CPU?
If that is the case then the fix will be included in Kudu 1.0.1, which is a
patch release scheduled to go out in a couple of weeks.
> Kudu master start failed
> ------------------------
>
> Key: KUDU-1660
> URL: https://issues.apache.org/jira/browse/KUDU-1660
> Project: Kudu
> Issue Type: Bug
> Components: master
> Affects Versions: 1.0.0
> Reporter: Jarred Li
>
> Kudu is installed with YUM in CentOS 6.5. Kudu master start failed with
> following warining:
> Log file created at: 2016/09/28 22:57:31
> Running on machine: n1
> Log line format: [IWEF]mmdd hh:mm:ss.uuuuuu threadid file:line] msg
> W0928 22:57:31.947437 3442 catalog_manager.cc:365] Catalog manager
> background task thread going to sleep: Service unavailable: Catalog manager
> is not initialized. State: 1
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
