Martin,
many thanks for your response. Finally I got a chance to try out your suggestion and exam the java environment of my node. about the site.csv, here is my current configuration. Hopefully, the only troubling one is the jdk package. for that value, I tried several different one: *java-1.6.0-openjdk, java-1.7.0-openjdk,java-1.6.0-openjdk.x86_64,java-1.7.0-openjdk.x86_64*. But keeping get the same error. The following is my csv and the jdk package info from yum. I must misunderstand some points here. /* site.csv */ " hadoop_head_node,hdfs003.demai.com hadoop_storage_dirs,/data/1,/data/2,/data/3,/data/4 bigtop_yumrepo_uri, http://bigtop.s3.amazonaws.com/releases/0.8.0/redhat/6/x86_64 jdk_package_name,*java-1.6.0-openjdk* components,hadoop,yarn,hbase " /* jdk packages */ [ptadm@hdfs003 pluginconf.d]$ yum list *OpenJDK* base | 3.7 kB 00:00 bigtop | 2.9 kB 00:00 epel | 4.4 kB 00:00 epel/primary_db | 6.7 MB 00:12 extras | 3.4 kB 00:00 puppetlabs-deps | 2.5 kB 00:00 puppetlabs-products | 2.5 kB 00:00 remi | 2.9 kB 00:00 remi/primary_db | 1.1 MB 00:01 updates | 3.4 kB 00:00 updates/primary_db | 4.4 MB 00:00 virtualbox | 951 B 00:00 virtualbox 26/26 Installed Packages java-1.6.0-openjdk.x86_64 1:1.6.0.0-6.1.13.4.el6_5 @updates java-1.6.0-openjdk-devel.x86_64 1:1.6.0.0-6.1.13.4.el6_5 @updates java-1.6.0-openjdk-javadoc.x86_64 1:1.6.0.0-6.1.13.4.el6_5 @updates java-1.7.0-openjdk.x86_64 1:1.7.0.65-2.5.1.2.el6_5 @updates java-1.7.0-openjdk-devel.x86_64 1:1.7.0.65-2.5.1.2.el6_5 @updates Available Packages java-1.6.0-openjdk.x86_64 1:1.6.0.35-1.13.7.1.el6_6 updates java-1.6.0-openjdk-demo.x86_64 1:1.6.0.35-1.13.7.1.el6_6 updates java-1.6.0-openjdk-devel.x86_64 1:1.6.0.35-1.13.7.1.el6_6 updates java-1.6.0-openjdk-javadoc.x86_64 1:1.6.0.35-1.13.7.1.el6_6 updates java-1.6.0-openjdk-src.x86_64 1:1.6.0.35-1.13.7.1.el6_6 updates java-1.7.0-openjdk.x86_64 1:1.7.0.85-2.6.1.3.el6_6 updates java-1.7.0-openjdk-demo.x86_64 1:1.7.0.85-2.6.1.3.el6_6 updates java-1.7.0-openjdk-devel.x86_64 1:1.7.0.85-2.6.1.3.el6_6 updates java-1.7.0-openjdk-javadoc.noarch 1:1.7.0.85-2.6.1.3.el6_6 updates java-1.7.0-openjdk-src.x86_64 1:1.7.0.85-2.6.1.3.el6_6 updates java-1.8.0-openjdk.x86_64 1:1.8.0.51-0.b16.el6_6 updates java-1.8.0-openjdk-demo.x86_64 1:1.8.0.51-0.b16.el6_6 updates java-1.8.0-openjdk-devel.x86_64 1:1.8.0.51-0.b16.el6_6 updates java-1.8.0-openjdk-headless.x86_64 1:1.8.0.51-0.b16.el6_6 updates java-1.8.0-openjdk-javadoc.noarch 1:1.8.0.51-0.b16.el6_6 updates java-1.8.0-openjdk-src.x86_64 1:1.8.0.51-0.b16.el6_6 updates On Wed, Jul 15, 2015 at 1:37 AM, Martin Bukatovic <[email protected]> wrote: > Hi Demai, > > see my reply inline: > > On 07/15/2015 12:18 AM, Demai Ni wrote: > > I am following instruction here: > > > > > https://cwiki.apache.org/confluence/display/BIGTOP/How+to+install+Bigtop+0.8.0+Hadoop+on+CentOS+6+with+Puppet > > > > > > to setup a 2-node clusters. But failed at very early stage: puppet > > apply. Well, quite possible that I made a small mistake somewhere, but I > > have no clue. > > > > > > the error location *site.pp:21 *points to jdk property. I do have a > > jdk1.7 on my system, and was hoping puppet will automatically install > > 1.6 as required by bigtop. > > You are right that puppet will install the jdk package based on value > of this property, but you need to make this package available in the > repositories of nodes you are deploying bigtop on first. > > That is because this jdk property is expected to be configured by > an admin deploying bigtop based on java available on theirs machines. > It doesn't magically try to download java package from somewhere > behind the scene. > > So in your case, when you already have java 1.7 installed on your > machines, you can > > * either check proper name of package for java 1.6 available in > repositories of your distribution and edit the property > accordingly > * or use java 1.7 you already have installed on your system > (but this may not work as official requirement of 0.8.0 > release is java 1.6) > > But looking at your example, you seem not to configure your > site.csv file at all. You need to properly fill out all > required values as described in the mentioned page, otherwise > you can't expect it to work. > > Hope it helps a bit. > > -- > Martin Bukatovic >
