[
https://issues.apache.org/jira/browse/BIGTOP-1736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14366702#comment-14366702
]
Evans Ye commented on BIGTOP-1736:
----------------------------------
Hi [~mackrorysd],
Sorry, the {{enable_local_repo}} feature is broken now. [~jayunit100]'s
BIGTOP-1733 fixed the problem but not yet committed though.
I've just tested and
{{http://bigtop01.cloudera.org:8080/view/Releases/job/Bigtop-0.8.0/label=centos6/6/artifact/output/}}
works fine in my environment. If I would be guessing, did you reserve a signle
space between components when configuring the components?
* DO NOT WORK: components: [hadoop,yarn]
* WORKS: components: [hadoop, yarn]
> Determine why SOLRCTL fails and add error messages to puppet.
> -------------------------------------------------------------
>
> Key: BIGTOP-1736
> URL: https://issues.apache.org/jira/browse/BIGTOP-1736
> Project: Bigtop
> Issue Type: Bug
> Components: solr
> Reporter: jay vyas
> Assignee: Sean Mackrory
>
> I tried testing solr spin up in bigtop.
> I noticed two things.
> 1) Zookeeper wasn't running when it attempted to do the solr setup/apply. I
> assume this is a bug, because, solrcloud reallly needs ZK from what i
> understand.
> 2) There is a cryptic error message... the below puppet logs show it is
> trying to run **init** on {{solrctl}} . Its not immediately clear why it
> fails. lets make puppet report the error better.
> {noformat}
> ==> bigtop1: Error: /bin/bash -c '/usr/bin/solrctl debug-dump | grep -q
> solr.xml || /usr/bin/solrctl init' returned 1 instead of one of [0]
> ==> bigtop1: Error: /Stage[main]/Solr::Server/Exec[solr init]/returns: change
> from notrun to 0 failed: /bin/bash -c '/usr/bin/solrctl debug-dump | grep -q
> sol
> r.xml || /usr/bin/solrctl init' returned 1 instead of one of [0]
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
