Either way: wiki update or opening a JIRA snd submitting a patch as Evans suggested. Perhaps the latter is even better considering that it fixes the issue instead of just describing it.
Regards, Cos On November 22, 2015 2:52:37 AM PST, David Starina <[email protected]> wrote: >So ... Should I update the wiki for the time being, until the issue is >fixed, or not? > >--David > >On Sun, Nov 22, 2015 at 6:13 AM, Evans Ye <[email protected]> wrote: > >> I think you can go submit a path to auto configure things properly. >The >> spirit of Bigtop Provisioner is to give you the environment with just >one >> click. ;) >> >> BTW thanks for discovering the issue, David. >> >> 2015-11-22 9:20 GMT+08:00 Konstantin Boudnik <[email protected]>: >> >>> Good find! Thanks for sharing. Do you mind adding this to the wiki >page as >>> well? >>> >>> Thanks! >>> Cos >>> >>> On Sun, Nov 22, 2015 at 12:02AM, David Starina wrote: >>> > It works once I disabled firewalld. CentOS 7 seems fo use >firewalld >>> instead >>> > of iptables, but Bigtop tries to configure iptables instead. >>> > >>> > --David >>> > >>> > On Sat, Nov 21, 2015 at 10:20 PM, David Starina < >>> [email protected]> >>> > wrote: >>> > >>> > > It seems the network was not configured properly (probably the >>> ipconfig >>> > > error I pasted previously). Any tip on how to setup network >settings >>> > > manually? When I run "hdfs dfsadmin -report" from the second >machine, >>> I >>> > > get: "report: No Route to Host from bigtop2.vagrant/10.10.10.12 >to >>> > > bigtop1.vagrant:8020 failed on socket timeout exception: >>> > > java.net.NoRouteToHostException: No route to host; For more >details >>> see: >>> > > http://wiki.apache.org/hadoop/NoRouteToHost"; >>> > > >>> > > --David >>> > > >>> > > On Sat, Nov 21, 2015 at 8:53 PM, David Starina < >>> [email protected]> >>> > > wrote: >>> > > >>> > >> Konstantin, >>> > >> >>> > >> Yes, I used the 1.0.0 release. Thank you - I will give the >nightly >>> builds >>> > >> a try. >>> > >> >>> > >> Best regards, >>> > >> David >>> > >> >>> > >> On Sat, Nov 21, 2015 at 8:18 PM, Konstantin Boudnik ><[email protected]> >>> > >> wrote: >>> > >> >>> > >>> David, >>> > >>> >>> > >>> if you're trying to install the cluster from release 1.0.0 >then YCSB >>> > >>> isn't a >>> > >>> part of it. Release work started before the components has >been >>> added. >>> > >>> You can try to use nightly builds from the master to add YCSB >>> package to >>> > >>> your >>> > >>> cluster >>> > >>> >>> > >>> >>> >http://ci.bigtop.apache.org/view/Bigtop-trunk/job/Bigtop-trunk-packages/ >>> > >>> >>> > >>> As for docker - it works pretty well, it seems, so you might >want to >>> > >>> give it a >>> > >>> try. >>> > >>> >>> > >>> Hope it helps, >>> > >>> Cos >>> > >>> >>> > >>> On Sat, Nov 21, 2015 at 08:07PM, David Starina wrote: >>> > >>> > Hi, >>> > >>> > >>> > >>> > I have tried to create a VM-based Hadoop cluster (is the >Docker >>> > >>> > installation complete/stable? On the Bigtop website it said >it is >>> a >>> > >>> work in >>> > >>> > progress, so I decided to go with the VM-based installation >for >>> now), >>> > >>> > following this guide: >>> > >>> > >>> > >>> >>> >https://cwiki.apache.org/confluence/display/BIGTOP/Bigtop+Provisioner+User+Guide >>> > >>> > >>> > >>> > Made the following changes to vagrantconfig.yaml, left >everything >>> else >>> > >>> at >>> > >>> > default (CentOS 7 installation): >>> > >>> > >>> > >>> > *memory_size: 3072* >>> > >>> > *num_instances: 2* >>> > >>> > *components: [hadoop, yarn, mahout, spark, ycsb]* >>> > >>> > Vagrant seemed to get a lot of the things right, but it did >end >>> with an >>> > >>> > error. Can you help me with that? I copied the errors (and >one >>> warning) >>> > >>> > that I got: >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> > *==> bigtop1: sed: can't read /etc/sysconfig/rngd: No such >file or >>> > >>> > directory==> bigtop1: Redirecting to /bin/systemctl start >>> > >>> rngd.service==> >>> > >>> > bigtop1: Redirecting to /bin/systemctl stop >iptables.service==> >>> > >>> bigtop1: >>> > >>> > Failed to issue method call: Unit iptables.service not >loaded.==> >>> > >>> bigtop1: >>> > >>> > error reading information on service iptables: No such file >or >>> > >>> directory==> >>> > >>> > bigtop1: Warning: The use of 'import' is deprecated at >>> > >>> > >>> > >>> >>> >/tmp/vagrant-puppet/manifests-f76206f1841b10444f0cea13160540f3/site.pp:71. >>> > >>> > See http://links.puppetlabs.com/puppet-import-deprecation >>> > >>> > <http://links.puppetlabs.com/puppet-import-deprecation>==> >>> bigtop1: >>> > >>> (at >>> > >>> > >/usr/share/ruby/vendor_ruby/puppet/parser/parser_support.rb:110:in >>> > >>> > `import')==> bigtop1: Error: Could not update: Execution of >>> '/bin/yum >>> > >>> -d 0 >>> > >>> > -e 0 -y list ycsb' returned 1: Error: No matching Packages >to >>> list==> >>> > >>> > bigtop1: Error: >/Stage[main]/Ycsb::Client/Package[ycsb]/ensure: >>> change >>> > >>> from >>> > >>> > absent to latest failed: Could not update: Execution of >'/bin/yum >>> -d 0 >>> > >>> -e 0 >>> > >>> > -y list ycsb' returned 1: Error: No matching Packages to >listThe >>> SSH >>> > >>> > command responded with a non-zero exit status. >Vagrantassumes >>> that this >>> > >>> > means the command failed. The output for this commandshould >be in >>> the >>> > >>> log >>> > >>> > above. Please read the output to determine whatwent wrong.* >>> > >>> > >>> > >>> > It seems the biggest error is the YCBS is not available >(should >>> any of >>> > >>> the >>> > >>> > other errors worry me?). What did I do wrong - is YCBS no >longer >>> > >>> available >>> > >>> > in Bigtop? It is on the list of effective values that the >guide >>> links >>> > >>> to. >>> > >>> > >>> > >>> > Best regards, >>> > >>> > David >>> > >>> >>> > >> >>> > >> >>> > > >>> >> >>
