Wataƙila ba asiri ba ne cewa shekarar da ta gabata shekara ce ta manyan canje-canje ga Apache Hadoop. A bara, Cloudera da Hortonworks sun haɗu (mahimmanci, siyan na ƙarshe), kuma Mapr, saboda matsalolin kuɗi masu tsanani, an sayar da su zuwa Hewlett Packard. Kuma idan 'yan shekarun baya, a cikin yanayin shigarwa na kan-gida, sau da yawa dole ne a yi zabi tsakanin Cloudera da Hortonworks, a yau, alas, ba mu da wannan zabi. Wani abin mamaki shi ne yadda Cloudera ta sanar a watan Fabrairu na wannan shekara cewa za ta daina fitar da tarukan da aka rarraba a cikin ma'ajiyar jama'a, kuma yanzu ana samun su ne kawai ta hanyar biyan kuɗi. Tabbas, har yanzu yana yiwuwa a zazzage sabbin nau'ikan CDH da HDP da aka fitar kafin ƙarshen 2019, kuma ana sa ran tallafi a gare su na tsawon shekaru ɗaya zuwa biyu. Amma me za a yi a gaba? Ga waɗanda suka biya biyan kuɗi a baya, babu abin da ya canza. Kuma ga waɗanda ba sa so su canza zuwa sigar da aka biya na rarrabawa, amma a lokaci guda suna so su sami damar karɓar sabbin nau'ikan abubuwan cluster, da faci da sauran sabuntawa, mun shirya wannan labarin. A ciki za mu yi la'akari da yiwuwar zaɓuɓɓuka don fita daga wannan yanayin.
Labarin ya fi bita. Ba zai ƙunshi kwatancen rarrabawa da cikakken nazarin su ba, kuma ba za a sami girke-girke don shigarwa da daidaita su ba. Me zai faru? Za mu yi magana a taƙaice game da irin wannan rarraba kamar Arenadata Hadoop, wanda ya cancanci kulawar mu saboda isar da shi, wanda ba kasafai ake samunsa ba a yau. Sannan za mu yi magana game da Vanilla Hadoop, musamman game da yadda za a iya “dafa shi” ta amfani da Apache Bigtop. Shirya? Sannan barka da zuwa cat.
Arenadata Hadoop
Wannan sabon sabon abu ne kuma, har yanzu, ƙanƙan sanann kayan rarrabawa na ci gaban gida. Abin takaici, a halin yanzu akan Habré akwai kawai .
Ana iya samun ƙarin bayani akan jami'in aikin. Sabbin sigogin rarraba sun dogara ne akan Hadoop 3.1.2 don sigar 3, da 2.8.5 don sigar 2.
Ana iya samun bayanai game da taswirar hanya .
Interface Manager Cluster Arenadata
Babban samfurin Arenadata shine , wanda aka yi amfani da shi don shigarwa, daidaitawa da kuma saka idanu daban-daban mafita software na kamfani. Ana rarraba ADCM kyauta, kuma ana faɗaɗa aikinta ta hanyar ƙara daure, waɗancan saiti ne na littattafan wasan kwaikwayo. Ganyayyaki sun kasu kashi biyu: kasuwanci da al'umma. Ana samun na ƙarshe don saukewa kyauta daga gidan yanar gizon Arenadata. Hakanan yana yiwuwa a haɓaka tarin ku kuma haɗa shi zuwa ADCM.
Don turawa da sarrafa Hadoop 3, ana ba da sigar al'umma ta tarin tare da ADCM, amma don Hadoop 2 akwai kawai a matsayin madadin. Dangane da ma'ajin ajiya tare da fakiti, suna buɗe don samun damar jama'a, ana iya saukar da su kuma shigar da su ta hanyar da aka saba don duk abubuwan da ke cikin gungu. Gabaɗaya, rarrabawar tana da ban sha'awa sosai. Na tabbata za a sami wadanda suka saba da mafita irin su Cloudera Manager da Ambari, kuma za su so ADCM da kanta. Ga wasu, zai kuma zama babbar ƙari cewa rarrabawa don sauya shigo da kaya.
Idan muka yi magana game da rashin amfani, za su kasance daidai da duk sauran rarraba Hadoop. Wato:
- Abin da ake kira "kulle mai sayarwa". Yin amfani da misalan Cloudera da Hortonworks, mun riga mun gane cewa koyaushe akwai haɗarin canza manufofin kamfani.
- Mahimman ragi a bayan Apache na sama.
Vanilla Hadoop
Kamar yadda ka sani, Hadoop ba samfura ne na monolithic ba, amma, a haƙiƙa, gabaɗayan sabis na galaxy da ke kewaye da tsarin fayil ɗin HDFS da aka rarraba. Mutane kaɗan ne za su sami isasshen gungu na fayil ɗaya. Wasu suna buƙatar Hive, wasu Presto, sannan akwai HBase da Phoenix; Ana ƙara amfani da Spark. Don ƙungiyar kade-kade da loda bayanai, Oozie, Sqoop da Flume ana samun wasu lokuta. Kuma idan batun tsaro ya taso, nan da nan Kerberos tare da Ranger ya zo a hankali.
Akwai nau'ikan nau'ikan abubuwan haɗin Hadoop na binaryar akan gidan yanar gizon kowane ɗayan ayyukan muhalli ta hanyar kwalta. Kuna iya zazzage su kuma fara shigarwa, amma tare da sharadi ɗaya: ban da haɗa fakitin kai tsaye daga binaries "raw", waɗanda galibi kuna son yi, ba za ku sami kwarin gwiwa kan dacewa da abubuwan abubuwan da aka zazzage tare da kowannensu ba. sauran. Zaɓin da aka fi so shine ginawa ta amfani da Apache Bigtop. Bigtop zai ba ku damar ginawa daga ma'ajiyar Apache maven, gudanar da gwaje-gwaje da gina fakiti. Amma, abin da ke da mahimmanci a gare mu, Bigtop zai tattara waɗannan nau'ikan abubuwan da za su dace da juna. Za mu yi magana game da shi dalla-dalla a ƙasa.
Apache Bigtop
Apache Bigtop kayan aiki ne don gini, tattarawa da gwada adadin
ayyukan bude tushen, kamar Hadoop da Greenplum. Bigtop yana da yawa
sakewa. A lokacin rubuce-rubuce, sabuwar barga ta saki shine sigar 1.4,
kuma a cikin master akwai 1.5. Daban-daban na sakewa suna amfani da nau'i daban-daban
aka gyara. Misali, don 1.4 Hadoop core abubuwan haɗin suna da sigar 2.8.5, kuma a cikin master
2.10.0. Haɗin abubuwan abubuwan da aka goyan baya kuma yana canzawa. Wani abu da ya wuce kuma
wanda ba a sabunta shi ba ya tafi, kuma a wurinsa ya zo wani sabon abu, mafi yawan buƙata, kuma
ba lallai ba ne wani abu daga dangin Apache kanta.
Bugu da kari, Bigtop yana da yawa .
Lokacin da muka fara saba da Bigtop, da farko mun yi mamakin girmansa, idan aka kwatanta da sauran ayyukan Apache, yaɗuwar jama'a da shahararsa, da kuma ƙaramar al'umma. Ya biyo baya daga wannan cewa akwai ƙarancin bayanai akan samfurin, kuma neman hanyoyin magance matsalolin da suka taso akan dandalin tattaunawa da jerin wasiƙu na iya ba su samar da komai kwata-kwata. Da farko, ya zama aiki mai wuyar gaske a gare mu don kammala cikakken taro na rarraba saboda fasalin kayan aiki da kansa, amma za mu yi magana game da wannan kadan daga baya.
A matsayin teaser, waɗanda a lokaci guda suna da sha'awar irin waɗannan ayyukan na sararin samaniyar Linux kamar Gentoo da LFS na iya samun jin daɗin yin aiki tare da wannan abu kuma mu tuna waɗancan lokutan “almara” lokacin da mu kanmu muke nema (ko ma rubutu) ginawa da sake gina Mozilla akai-akai tare da sabbin faci.
Babban fa'idar Bigtop shine buɗewa da haɓakar kayan aikin da aka dogara da su. Ya dogara ne akan Gradle da Apache Maven. Gradle sananne ne a matsayin kayan aikin da Google ke amfani da shi don gina Android. Yana da sassauƙa, kuma, kamar yadda suke faɗa, “an gwada yaƙi.” Maven daidaitaccen kayan aiki ne don ayyukan gine-gine a Apache kanta, kuma tunda yawancin samfuransa ana fitar da su ta hanyar Maven, ba za a iya yin hakan ba tare da shi anan ba. Yana da kyau a kula da POM (samfurin abu na aikin) - fayil ɗin xml "mahimmanci" wanda ke kwatanta duk abin da ake bukata don Maven yayi aiki tare da aikin ku, wanda aka gina duk aikin. Daidai a
sassan Maven kuma akwai wasu cikas waɗanda masu amfani da Bigtop na farko sukan ci karo da su.
Yi aiki
To a ina ya kamata ku fara? Jeka shafin zazzagewa kuma zazzage sabon sigar barga a matsayin ma'ajiya. A can kuma kuna iya samun kayan tarihi na binary wanda Bigtop ya tattara. Af, a tsakanin manajojin fakiti na gama-gari, YUM da APT ana tallafawa.
A madadin, zaku iya zazzage sabuwar bargawar sakin kai tsaye daga
github:
$ git clone --branch branch-1.4 https://github.com/apache/bigtop.gitCloning a cikin "babban"…
remote: Enumerating objects: 46, done.
remote: Counting objects: 100% (46/46), done.
remote: Compressing objects: 100% (41/41), done.
remote: Total 40217 (delta 14), reused 10 (delta 1), pack-reused 40171
Получение объектов: 100% (40217/40217), 43.54 MiB | 1.05 MiB/s, готово.
Определение изменений: 100% (20503/20503), готово.
Updating files: 100% (1998/1998), готово.Sakamakon ./bigtop directory yayi kama da wannan:
./bigtop-bigpetstore - aikace-aikacen demo, misalan roba
./bigtop-ci - CI kayan aikin, jenkins
./bigtop-data-generators - ƙirƙira bayanai, synthetics, don gwajin hayaki, da sauransu.
./bigtop-deploy - tura kayan aikin
./bigtop-packages - saiti, rubutun, faci don haɗuwa, babban ɓangaren kayan aiki
./bigtop-test-framework - tsarin gwaji
./bigtop-tests - gwaje-gwajen kansu, lodi da hayaki
./bigtop_toolchain - yanayi don haɗuwa, shirya yanayin don kayan aiki don aiki
./build - gina littafin aiki
./dl - kundin adireshi don abubuwan da aka sauke
./docker - gini a cikin hotunan docker, gwaji
./gradle - gradle config
./output – directory inda ginin kayan tarihi ke tafiya
./provisioner - tanadi
Abu mafi ban sha'awa a gare mu a wannan mataki shine babban saitin ./bigtop/bigtop.bom, wanda a cikinsa muke ganin duk abubuwan da aka goyan baya tare da sigogin. Wannan shi ne inda za mu iya ƙayyade nau'in samfurin daban-daban (idan ba zato ba tsammani muna so mu yi ƙoƙarin gina shi) ko sigar ginin (idan, alal misali, mun ƙara faci mai mahimmanci).
Subdirectory shima yana da sha'awa sosai ./bigtop/bigtop-packages, wanda ke da alaƙa kai tsaye da tsarin haɗa abubuwan haɗin gwiwa da fakiti tare da su.
Don haka, mun zazzage ma'ajiyar, mun cire shi ko sanya clone daga github, za mu iya fara gini?
A'a, bari mu fara shirya yanayin.
Shirya Muhalli
Kuma a nan muna buƙatar ƙaramin ja da baya. Don gina kusan kowane samfuri ko žasa mai rikitarwa, kuna buƙatar takamaiman yanayi - a cikin yanayinmu, wannan shine JDK, ɗakunan karatu iri ɗaya, fayilolin rubutu, da sauransu, kayan aikin, misali, ant, ivy2 da ƙari mai yawa. Ɗaya daga cikin zaɓuɓɓukan don samun yanayin da kuke buƙata don Bigtop shine shigar da abubuwan da suka dace akan ginin ginin. Zan iya yin kuskure a cikin tarihin tarihin, amma da alama cewa tare da sigar 1.0 akwai kuma zaɓi don ginawa a cikin abubuwan da aka riga aka tsara da kuma samun damar hotuna Docker, waɗanda za'a iya samu anan.
Game da shirya yanayin, akwai mataimaki ga wannan - Puppet.
Kuna iya amfani da umarni masu zuwa, gudu daga tushen directory
kayan aiki, ./bigtop:
./gradlew toolchain
./gradlew toolchain-devtools
./gradlew toolchain-puppetmodules
Ko kai tsaye ta hanyar tsana:
puppet apply --modulepath=<path_to_bigtop> -e "include bigtop_toolchain::installer"
puppet apply --modulepath=<path_to_bigtop> -e "include bigtop_toolchain::deployment-tools"
puppet apply --modulepath=<path_to_bigtop> -e "include bigtop_toolchain::development-tools"Abin takaici, matsaloli na iya tasowa a wannan matakin. Shawarar gabaɗaya anan ita ce a yi amfani da rarraba mai goyan baya, har zuwa yau akan mai masaukin ginin, ko gwada hanyar docker.
Majalisar
Me za mu iya ƙoƙarin tattarawa? Za a bayar da amsar wannan tambayar ta fitowar umarnin
./gradlew tasks
A cikin sashin ayyuka na Kunshin akwai samfura da yawa waɗanda kayan tarihi ne na ƙarshe na Bigtop.
Ana iya gano su ta hanyar suffix -rpm ko -pkg-ind (a yanayin ginin
in docker). A cikin yanayinmu, mafi ban sha'awa shine Hadoop.
Mu yi ƙoƙarin ginawa a cikin mahallin ginin uwar garken mu:
./gradlew hadoop-rpmBigtop da kansa zai sauke mahimman hanyoyin da ake buƙata don takamaiman sashi kuma ya fara haɗuwa. Don haka, aikin kayan aikin ya dogara ne akan ma'ajin Maven da sauran hanyoyin, wato, yana buƙatar shiga Intanet.
Yayin aiki, ana samar da daidaitaccen fitarwa. Wani lokaci shi da saƙon kuskure na iya taimaka maka fahimtar abin da ba daidai ba. Kuma wani lokacin kuna buƙatar samun ƙarin bayani. A wannan yanayin yana da daraja ƙara muhawara --info ko --debug, kuma yana iya zama da amfani –stacktrace. Akwai hanya mai dacewa don samar da saitin bayanai don samun dama ga jerin aikawasiku na gaba, maɓalli --scan.
Tare da taimakonsa, bigtop zai tattara duk bayanan kuma ya sanya shi a cikin gradle, bayan haka zai samar da hanyar haɗi,
ta hanyar bin abin, wanda ya cancanta zai iya fahimtar dalilin da yasa majalisar ta gaza.
Da fatan za a sani cewa wannan zaɓi na iya fallasa bayanan da ba ku so, kamar sunayen masu amfani, nodes, masu canjin yanayi, da sauransu, don haka a kula.
Sau da yawa kurakurai sakamakon rashin iya samun kowane abubuwan da ake buƙata don haɗuwa. Yawanci, zaku iya gyara matsalar ta hanyar ƙirƙirar faci don gyara wani abu a cikin maɓuɓɓuka, misali, adireshi a cikin pom.xml a cikin tushen tushen tushen. Ana yin wannan ta hanyar ƙirƙira da sanya shi a cikin littafin da ya dace ./bigtop/bigtop-packages/src/common/oozie/ faci, misali, a cikin tsari patch2-fix.diff.
--- a/pom.xml
+++ b/pom.xml
@@ -136,7 +136,7 @@
<repositories>
<repository>
<id>central</id>
- <url>http://repo1.maven.org/maven2</url>
+ <url>https://repo1.maven.org/maven2</url>
<snapshots>
<enabled>false</enabled>
</snapshots>
Mafi mahimmanci, a lokacin karanta wannan labarin, ba lallai ne ku gyara abin da ke sama ba.
Lokacin gabatar da kowane faci da canje-canje ga tsarin taro, ƙila ka buƙaci “sake saita” taron ta amfani da umarnin tsaftacewa:
./gradlew hadoop-clean
> Task :hadoop_vardefines
> Task :hadoop-clean
BUILD SUCCESSFUL in 5s
2 actionable tasks: 2 executedWannan aikin zai mayar da duk canje-canje zuwa taron wannan bangaren, bayan haka za a sake yin taron. A wannan lokacin za mu yi ƙoƙarin gina aikin a cikin hoton docker:
./gradlew -POS=centos-7 -Pprefix=1.2.1 hadoop-pkg-ind
> Task :hadoop-pkg-ind
Building 1.2.1 hadoop-pkg on centos-7 in Docker...
+++ dirname ./bigtop-ci/build.sh
++ cd ./bigtop-ci/..
++ pwd
+ BIGTOP_HOME=/tmp/bigtop
+ '[' 6 -eq 0 ']'
+ [[ 6 -gt 0 ]]
+ key=--prefix
+ case $key in
+ PREFIX=1.2.1
+ shift
+ shift
+ [[ 4 -gt 0 ]]
+ key=--os
+ case $key in
+ OS=centos-7
+ shift
+ shift
+ [[ 2 -gt 0 ]]
+ key=--target
+ case $key in
+ TARGET=hadoop-pkg
+ shift
+ shift
+ [[ 0 -gt 0 ]]
+ '[' -z x ']'
+ '[' -z x ']'
+ '[' '' == true ']'
+ IMAGE_NAME=bigtop/slaves:1.2.1-centos-7
++ uname -m
+ ARCH=x86_64
+ '[' x86_64 '!=' x86_64 ']'
++ docker run -d bigtop/slaves:1.2.1-centos-7 /sbin/init
+
CONTAINER_ID=0ce5ac5ca955b822a3e6c5eb3f477f0a152cd27d5487680f77e33fbe66b5bed8
+ trap 'docker rm -f
0ce5ac5ca955b822a3e6c5eb3f477f0a152cd27d5487680f77e33fbe66b5bed8' EXIT
....
много вывода
....
Wrote: /bigtop/build/hadoop/rpm/RPMS/x86_64/hadoop-2.8.5-1.el7.x86_64.rpm
Wrote: /bigtop/build/hadoop/rpm/RPMS/x86_64/hadoop-hdfs-2.8.5-1.el7.x86_64.rpm
Wrote: /bigtop/build/hadoop/rpm/RPMS/x86_64/hadoop-yarn-2.8.5-1.el7.x86_64.rpm
Wrote: /bigtop/build/hadoop/rpm/RPMS/x86_64/hadoop-mapreduce-2.8.5-1.el7.x86_64.rpm
Wrote: /bigtop/build/hadoop/rpm/RPMS/x86_64/hadoop-hdfs-namenode-2.8.5-1.el7.x86_64.rpm
Wrote: /bigtop/build/hadoop/rpm/RPMS/x86_64/hadoop-hdfs-secondarynamenode-2.8.5-
1.el7.x86_64.rpm
Wrote: /bigtop/build/hadoop/rpm/RPMS/x86_64/hadoop-hdfs-zkfc-2.8.5-1.el7.x86_64.rpm
Wrote: /bigtop/build/hadoop/rpm/RPMS/x86_64/hadoop-hdfs-journalnode-2.8.5-
1.el7.x86_64.rpm
Wrote: /bigtop/build/hadoop/rpm/RPMS/x86_64/hadoop-hdfs-datanode-2.8.5-1.el7.x86_64.rpm
Wrote: /bigtop/build/hadoop/rpm/RPMS/x86_64/hadoop-httpfs-2.8.5-1.el7.x86_64.rpm
Wrote: /bigtop/build/hadoop/rpm/RPMS/x86_64/hadoop-yarn-resourcemanager-2.8.5-
1.el7.x86_64.rpm
Wrote: /bigtop/build/hadoop/rpm/RPMS/x86_64/hadoop-yarn-nodemanager-2.8.5-
1.el7.x86_64.rpm
Wrote: /bigtop/build/hadoop/rpm/RPMS/x86_64/hadoop-yarn-proxyserver-2.8.5-
1.el7.x86_64.rpm
Wrote: /bigtop/build/hadoop/rpm/RPMS/x86_64/hadoop-yarn-timelineserver-2.8.5-
1.el7.x86_64.rpm
Wrote: /bigtop/build/hadoop/rpm/RPMS/x86_64/hadoop-mapreduce-historyserver-2.8.5-
1.el7.x86_64.rpm
Wrote: /bigtop/build/hadoop/rpm/RPMS/x86_64/hadoop-client-2.8.5-1.el7.x86_64.rpm
Wrote: /bigtop/build/hadoop/rpm/RPMS/x86_64/hadoop-conf-pseudo-2.8.5-1.el7.x86_64.rpm
Wrote: /bigtop/build/hadoop/rpm/RPMS/x86_64/hadoop-doc-2.8.5-1.el7.x86_64.rpm
Wrote: /bigtop/build/hadoop/rpm/RPMS/x86_64/hadoop-libhdfs-2.8.5-1.el7.x86_64.rpm
Wrote: /bigtop/build/hadoop/rpm/RPMS/x86_64/hadoop-libhdfs-devel-2.8.5-1.el7.x86_64.rpm
Wrote: /bigtop/build/hadoop/rpm/RPMS/x86_64/hadoop-hdfs-fuse-2.8.5-1.el7.x86_64.rpm
Wrote: /bigtop/build/hadoop/rpm/RPMS/x86_64/hadoop-debuginfo-2.8.5-1.el7.x86_64.rpm
+ umask 022
+ cd /bigtop/build/hadoop/rpm//BUILD
+ cd hadoop-2.8.5-src
+ /usr/bin/rm -rf /bigtop/build/hadoop/rpm/BUILDROOT/hadoop-2.8.5-1.el7.x86_64
Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.uQ2FCn
+ exit 0
+ umask 022
Executing(--clean): /bin/sh -e /var/tmp/rpm-tmp.CwDb22
+ cd /bigtop/build/hadoop/rpm//BUILD
+ rm -rf hadoop-2.8.5-src
+ exit 0
[ant:touch] Creating /bigtop/build/hadoop/.rpm
:hadoop-rpm (Thread[Task worker for ':',5,main]) completed. Took 38 mins 1.151 secs.
:hadoop-pkg (Thread[Task worker for ':',5,main]) started.
> Task :hadoop-pkg
Task ':hadoop-pkg' is not up-to-date because:
Task has not declared any outputs despite executing actions.
:hadoop-pkg (Thread[Task worker for ':',5,main]) completed. Took 0.0 secs.
BUILD SUCCESSFUL in 40m 37s
6 actionable tasks: 6 executed
+ RESULT=0
+ mkdir -p output
+ docker cp
ac46014fd9501bdc86b6c67d08789fbdc6ee46a2645550ff6b6712f7d02ffebb:/bigtop/build .
+ docker cp
ac46014fd9501bdc86b6c67d08789fbdc6ee46a2645550ff6b6712f7d02ffebb:/bigtop/output .
+ docker rm -f ac46014fd9501bdc86b6c67d08789fbdc6ee46a2645550ff6b6712f7d02ffebb
ac46014fd9501bdc86b6c67d08789fbdc6ee46a2645550ff6b6712f7d02ffebb
+ '[' 0 -ne 0 ']'
+ docker rm -f ac46014fd9501bdc86b6c67d08789fbdc6ee46a2645550ff6b6712f7d02ffebb
Error: No such container:
ac46014fd9501bdc86b6c67d08789fbdc6ee46a2645550ff6b6712f7d02ffebb
BUILD SUCCESSFUL in 41m 24s
1 actionable task: 1 executedAn yi ginin a ƙarƙashin CentOS, amma kuma ana iya yin shi a ƙarƙashin Ubuntu:
./gradlew -POS=ubuntu-16.04 -Pprefix=1.2.1 hadoop-pkg-indBaya ga fakitin gini don rarrabawar Linux daban-daban, kayan aikin na iya ƙirƙirar wurin ajiya tare da fakitin da aka haɗa, misali:
./gradlew yumHakanan zaka iya tunawa game da gwajin hayaki da turawa a Docker.
Ƙirƙiri tari na nodes uku:
./gradlew -Pnum_instances=3 docker-provisionerGudanar da gwaje-gwajen hayaki a cikin gungu na nodes uku:
./gradlew -Pnum_instances=3 -Prun_smoke_tests docker-provisionerShare gungu:
./gradlew docker-provisioner-destroySami umarni don haɗa cikin kwantenan docker:
./gradlew docker-provisioner-sshNuna hali:
./gradlew docker-provisioner-statusKuna iya karanta ƙarin game da ayyukan turawa a cikin takaddun.
Idan muka yi magana game da gwaje-gwaje, akwai quite babban adadin su, yafi hayaki da hadewa. Binciken su ya wuce iyakar wannan labarin. Bari in faɗi cewa haɗa kayan rarraba ba aiki mai wahala bane kamar yadda ake gani da farko. Mun yi nasarar tattarawa da gwada gwaje-gwaje a kan dukkan abubuwan da muke amfani da su wajen samarwa, kuma ba mu sami matsala ba wajen tura su da yin ayyuka na yau da kullun a yanayin gwajin.
Baya ga abubuwan da ke akwai a cikin Bigtop, yana yiwuwa a ƙara wani abu, har ma da haɓaka software na ku. Duk wannan an sarrafa shi daidai kuma ya dace da ra'ayin CI/CD.
ƙarshe
Babu shakka, rabon da aka haɗa ta wannan hanya bai kamata a aika da sauri zuwa samarwa ba. Kuna buƙatar fahimtar cewa idan akwai buƙatar gaske don ginawa da tallafawa rarraba ku, to kuna buƙatar saka kuɗi da lokaci a cikin wannan.
Koyaya, a hade tare da madaidaiciyar hanya da ƙwararrun ƙungiyar, yana yiwuwa a yi ba tare da mafita na kasuwanci ba.
Yana da mahimmanci a lura cewa aikin Bigtop da kansa yana buƙatar ci gaba kuma ba ya bayyana ana haɓakawa sosai a yau. Hasashen Hadoop 3 ya fito a ciki shima ba a san shi ba. Af, idan kuna da ainihin buƙatar gina Hadoop 3, zaku iya duba. daga Arenadata, wanda, ban da ma'auni
Akwai ƙarin ƙarin abubuwan haɗin gwiwa (Ranger, Knox, NiFi).
Amma ga Rostelecom, a gare mu Bigtop yana ɗaya daga cikin zaɓuɓɓukan da ake la'akari a yau. Ko mun zaɓa ko ba mu zaɓa ba, lokaci zai nuna.
shafi
Don haɗa sabon sashi a cikin taron, kuna buƙatar ƙara bayaninsa zuwa bigtop.bom da ./bigtop-packages. Kuna iya ƙoƙarin yin hakan ta hanyar kwatanci tare da abubuwan da ke akwai. Yi ƙoƙarin gano shi. Ba shi da wahala kamar yadda ake gani a kallon farko.
Me kuke tunani? Za mu yi farin cikin ganin ra'ayin ku a cikin sharhi kuma mun gode da hankalin ku!
Kungiyar kula da bayanai ta Rostelecom ce ta shirya labarin
source: www.habr.com