Hi Arvind, For production usage, you may need to build impala with the -release flag. For deployment, you will need to manually copy the artifacts to other nodes and set up required configuration files there.
There is a patch under review that can build a DEB/RPM package for deployment: https://gerrit.cloudera.org/c/18939/ It also has scripts for launching impala services. You can have a try once your build succeeds. Welcome for any feedback! BTW, looking for reviewers for that patch. It still needs another +1 from the committers. Regards, Quanlong On Mon, Feb 6, 2023 at 8:49 PM Arvind Dige <arvind.d...@ellicium.com> wrote: > Hi Community, > > @LaszloG > Yes, the issue may be due to resource crunch. So I will try to implement > it with higher resources. > > Till time, Just want to ask a simple question, can we use this impala in a > production environment? or is it only a standalone cluster for test > purposes? > Because I observed that build will not use multiple servers, rather it > creates 3 partitions on the same server itself as a master, node1 & node2. > > Regards, > Arvind > > > On Mon, Feb 6, 2023 at 10:34 AM Arvind Dige <arvind.d...@ellicium.com> > wrote: > > > Hi Joe, > > > > Any resolution or update on my problem? > > > > Regards, > > Arvind Dige > > > > On Fri, Feb 3, 2023 at 6:37 PM Arvind Dige <arvind.d...@ellicium.com> > > wrote: > > > >> Hi Joe, > >> I have recreated the issue and sharing the logs for the same with you. > >> Please use below links for build_logs and hmaster logs from the path as > you > >> mentioned in the above email. > >> > >> Build_logs => > >> > https://drive.google.com/file/d/126SfDWuMIkoY3QClhQzRhd3d1LfgeFwb/view?usp=sharing > >> hmaster_logs => > >> > https://drive.google.com/file/d/1nYsGqyZ2gpfawv7umAddmBuuOVGXvA7q/view?usp=sharing > >> > >> Also I have tried with different user on different machines and facing > >> the same issue there also. > >> With request, If possible please answer my questions from previous > mails. > >> > >> Thanks & Regards, > >> Arvind Dige > >> > >> On Fri, Feb 3, 2023 at 11:26 AM Arvind Dige <arvind.d...@ellicium.com> > >> wrote: > >> > >>> HI Joe, > >>> > >>> Due to some work I lost progress on the same work so I am unable to > >>> provide the logs for the same. I am trying to recreate the same issue. > >>> Also as you mentioned about root user I will try to build the impala > >>> using another user. > >>> But I have some questions like, > >>> > >>> 1) Is it needed to launch a mini cluster before starting impala? > >>> 2) Can we start impalad, catalogd or statestored roles individually to > >>> make impala works? > >>> 3) As I worked on CDH & CDP, is it possible to add one or more impala > >>> roles(components) on different nodes (How the role allocation works in > >>> impala)? > >>> 4) Also if i successfully build the impala, for node addition is it > >>> required to build impala separately on that node or how can we proceed > for > >>> the same? > >>> > >>> I will update you with the logs once I regenerate the issue. > >>> > >>> Thanks & Regards, > >>> Arvind Dige > >>> > >>> On Fri, Feb 3, 2023 at 12:52 AM Joe McDonnell < > joemcdonn...@cloudera.com> > >>> wrote: > >>> > >>>> Hi Arvind, > >>>> > >>>> Compilation succeeds, and now it is starting up the Hadoop components > >>>> that we use for testing. In this case, it is starting up HBase and > failing. > >>>> Additional logs will be in the logs/cluster/hbase/ directory. In this > >>>> case, /root/Impala/logs/cluster/hbase/hbase-master-master-hadoop.out > should > >>>> contain more info. > >>>> > >>>> We do regularly use Ubuntu 20 for development, so we expect Impala to > >>>> work. We do not test running as root user, so I don't know if that > would > >>>> matter or not. > >>>> > >>>> Thanks, > >>>> Joe > >>>> > >>>> On Thu, Feb 2, 2023 at 9:17 AM Arvind Dige <arvind.d...@ellicium.com> > >>>> wrote: > >>>> > >>>>> Hi Joe, > >>>>> > >>>>> Thanks for your reply. > >>>>> Please find the below gdrive link which is publically accessible > >>>>> > >>>>> > https://drive.google.com/file/d/1rvJRWXephJJlV1Ij_QwkorFlUQx2fhdB/view?usp=sharing > >>>>> > >>>>> Thanks & Regards, > >>>>> Arvind Dige > >>>>> > >>>>> On Thu, Feb 2, 2023 at 10:38 PM Joe McDonnell < > >>>>> joemcdonn...@cloudera.com> wrote: > >>>>> > >>>>>> Hi Arvind, > >>>>>> > >>>>>> Unfortunately, the email servers for these mailing lists strip > >>>>>> attachments. Can you upload the log to some public location and > provide a > >>>>>> link? > >>>>>> > >>>>>> Thanks, > >>>>>> Joe > >>>>>> > >>>>>> On Wed, Feb 1, 2023 at 10:07 PM Arvind Dige < > arvind.d...@ellicium.com> > >>>>>> wrote: > >>>>>> > >>>>>>> Hi Team, I am facing an issue while building impala, can you help > me > >>>>>>> to troubleshoot it? > >>>>>>> I am trying to build impala on ubuntu-20.04 using > >>>>>>> https://cwiki.apache.org/confluence/display/IMPALA/Building+Impala > >>>>>>> . > >>>>>>> <https://stackoverflow.com/posts/75282210/timeline> > >>>>>>> > >>>>>>> I am able to see HDFS, HIVE, HBase, Ranger components are > downloaded > >>>>>>> but the build was failing with "Could not get one or more nodes" > >>>>>>> > >>>>>>> I am attaching the log file for reference, please check and > respond. > >>>>>>> > >>>>>>> Thanks & Regards, > >>>>>>> > >>>>>>> Arvind Dige > >>>>>>> > >>>>>>> Privileged/Confidential information may be contained in this > message > >>>>>>> and may be subject to legal privilege. Access to this e-mail by > anyone > >>>>>>> other than the intended is unauthorized. If you are not the > >>>>>>> intended recipient (or responsible for delivery of the message to > such > >>>>>>> person), you may not use, copy, distribute or deliver to anyone > this > >>>>>>> message (or any part of its contents ) or take any action in > reliance on > >>>>>>> it. In such case, you should destroy this message, and notify us > >>>>>>> immediately. If you have received this email in error, please > notify us > >>>>>>> immediately by e-mail or telephone and delete the e-mail from any > computer. > >>>>>>> If you or your employer does not consent to internet e-mail > messages of > >>>>>>> this kind, please notify us immediately by e-mail. All reasonable > >>>>>>> precautions have been taken to ensure no viruses are present in > this > >>>>>>> e-mail. As our company cannot accept responsibility for any loss > or damage > >>>>>>> arising from the use of this e-mail or attachments we recommend > that you > >>>>>>> subject these to your virus checking procedures prior to use. The > views, > >>>>>>> opinions, conclusions and other information expressed in this > electronic > >>>>>>> mail are not given or endorsed by the company unless otherwise > indicated by > >>>>>>> an authorized representative independent of this message. > >>>>>> > >>>>>> > >>>>> Privileged/Confidential information may be contained in this message > >>>>> and may be subject to legal privilege. Access to this e-mail by > anyone > >>>>> other than the intended is unauthorized. If you are not the intended > >>>>> recipient (or responsible for delivery of the message to such > person), you > >>>>> may not use, copy, distribute or deliver to anyone this message (or > any > >>>>> part of its contents ) or take any action in reliance on it. In such > case, > >>>>> you should destroy this message, and notify us immediately. If you > have > >>>>> received this email in error, please notify us immediately by e-mail > or > >>>>> telephone and delete the e-mail from any computer. If you or your > employer > >>>>> does not consent to internet e-mail messages of this kind, please > notify us > >>>>> immediately by e-mail. All reasonable precautions have been taken to > ensure > >>>>> no viruses are present in this e-mail. As our company cannot accept > >>>>> responsibility for any loss or damage arising from the use of this > e-mail > >>>>> or attachments we recommend that you subject these to your virus > checking > >>>>> procedures prior to use. The views, opinions, conclusions and other > >>>>> information expressed in this electronic mail are not given or > endorsed by > >>>>> the company unless otherwise indicated by an authorized > representative > >>>>> independent of this message. > >>>> > >>>> > > -- > Privileged/Confidential information may be contained in this message and > may be subject to legal privilege. Access to this e-mail by anyone other > than the intended is unauthorized. If you are not the intended recipient > (or responsible for delivery of the message to such person), you may not > use, copy, distribute or deliver to anyone this message (or any part of > its > contents ) or take any action in reliance on it. In such case, you should > destroy this message, and notify us immediately. If you have received this > email in error, please notify us immediately by e-mail or telephone and > delete the e-mail from any computer. If you or your employer does not > consent to internet e-mail messages of this kind, please notify us > immediately by e-mail. All reasonable precautions have been taken to > ensure > no viruses are present in this e-mail. As our company cannot accept > responsibility for any loss or damage arising from the use of this e-mail > or attachments we recommend that you subject these to your virus checking > procedures prior to use. The views, opinions, conclusions and other > information expressed in this electronic mail are not given or endorsed by > the company unless otherwise indicated by an authorized representative > independent of this message. >
