impala-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pradeep Nayak <pradeep1...@gmail.com>
Subject Re: How to install the custom built impala
Date Tue, 13 Sep 2016 23:13:09 GMT
Okay thanks Tim. I tried that.

I am seeing the below error, once I repalced the impalad and
libfesupport.so. Same errors for statestore and catalogd.

+ true
+ export IMPALA_BIN=/opt/cloudera/parcels/CDH-5.8.0-1.cdh5.8.0.p0.42/lib/impala/sbin-debug
+ IMPALA_BIN=/opt/cloudera/parcels/CDH-5.8.0-1.cdh5.8.0.p0.42/lib/impala/sbin-debug
+ [[ true = '' ]]
+ '[' impalad = impalad ']'
+ exec /opt/cloudera/parcels/CDH-5.8.0-1.cdh5.8.0.p0.42/lib/impala/../../bin/impalad
--flagfile=/run/cloudera-scm-agent/process/92-impala-IMPALAD/impala-conf/impalad_flags
/opt/cloudera/parcels/CDH-5.8.0-1.cdh5.8.0.p0.42/lib/impala/sbin-debug/impalad:
error while loading shared libraries: libTestUtil.so: cannot open
shared object file: No such file or directory


Regards,
Pradeep Nayak

http://pradeepnayak.in
http://twitter.com/_prdp

On Tue, Sep 13, 2016 at 2:16 PM, Tim Armstrong <tarmstrong@cloudera.com>
wrote:

> If the statestored and catalogd symlinks point to the new impalad binary
> then you're good.
>
> On Tue, Sep 13, 2016 at 2:02 PM, Pradeep Nayak <pradeep1288@gmail.com>
> wrote:
>
>> My confusion should I update the bin location or the sbin location here
>> : /opt/cloudera/parcels/CDH/lib/impala/sbin. Here the catalogd and
>> statestored appear to be symlinks to impalad.
>>
>> Regards,
>> Pradeep Nayak
>>
>> http://pradeepnayak.in
>> http://twitter.com/_prdp
>>
>> On Tue, Sep 13, 2016 at 1:57 PM, Pradeep Nayak <pradeep1288@gmail.com>
>> wrote:
>>
>>> Okay, I can override impalad at /opt/cloudera/parcels/CDH-5
>>> .8.0-1.cdh5.8.0.p0.42/bin/impalad with the one which I have built. How
>>> about catalogd and statestored ?
>>>
>>> Regards,
>>> Pradeep Nayak
>>>
>>> http://pradeepnayak.in
>>> http://twitter.com/_prdp
>>>
>>> On Mon, Sep 12, 2016 at 3:41 PM, Matthew Jacobs <mj@cloudera.com> wrote:
>>>
>>>> Correct, impala-data-source-api*.jar rarely changes, but it will when
>>>> we rename our java packages: https://gerrit.cloudera.org/#/c/3937/
>>>>
>>>> If you go through this process again with a build after that change
>>>> goes in, then you'll need to update that jar.
>>>>
>>>> You can build it by running mvn package in Impala/ext-data-source.
>>>>
>>>> On Mon, Sep 12, 2016 at 3:29 PM, Tim Armstrong <tarmstrong@cloudera.com>
>>>> wrote:
>>>> > It looks like impala-data-source* may not be built in all case. It
>>>> doesn't
>>>> > really change much if at all so I doubt you will need to update it
>>>> anyway.
>>>> >
>>>> > P.S. I agree with Jim, this is exactly the kind of question this list
>>>> is
>>>> > for.
>>>> >
>>>> > On Mon, Sep 12, 2016 at 2:08 PM, Pradeep Nayak <pradeep1288@gmail.com
>>>> >
>>>> > wrote:
>>>> >
>>>> >> So here is what I understand:
>>>> >>
>>>> >> I need to pick the files built here: /home/ubuntu/Impala/be/
>>>> >> build/debug/service
>>>> >>
>>>> >> ubuntu@ip-172-30-2-163:~/Impala/be/build/debug/service$ ls -l
>>>> >> total 330928
>>>> >> -rwxrwxr-x 1 ubuntu ubuntu 59342696 Sep 12 19:25 hs2-util-test
>>>> >> *-rwxrwxr-x 1 ubuntu ubuntu 58803080 Sep 12 19:24 impalad*
>>>> >> *-rwxrwxr-x 1 ubuntu ubuntu 63169736 Sep 12 19:25 libfesupport.so*
>>>> >> *-rwxrwxr-x 1 ubuntu ubuntu 37056896 Sep  6 21:41 libService.so*
>>>> >> -rwxrwxr-x 1 ubuntu ubuntu 59526680 Sep 12 19:25 query-options-test
>>>> >> -rwxrwxr-x 1 ubuntu ubuntu 60960616 Sep 12 19:25 session-expiry-test
>>>> >> ubuntu@ip-172-30-2-163:~/Impala/be/build/debug/service$
>>>> >>
>>>> >> and replace it with one on my test cluster for backend part.
>>>> >>
>>>> >>
>>>> >> For the frontend, i need to pick the below file:
>>>> >>
>>>> >> */home/ubuntu/Impala/fe/target/impala-frontend-0.1-SNAPSHOT.jar
*
>>>> >>
>>>> >>
>>>> >> I couldn't find the impala-data-source-api*.jar file
>>>> >>
>>>> >>
>>>> >> Regards,
>>>> >> Pradeep Nayak
>>>> >>
>>>> >> http://pradeepnayak.in
>>>> >> http://twitter.com/_prdp
>>>> >>
>>>> >> On Mon, Sep 12, 2016 at 1:26 PM, Tim Armstrong <
>>>> tarmstrong@cloudera.com>
>>>> >> wrote:
>>>> >>
>>>> >>> I don't think this is documented anywhere. You would need to
>>>> replace the
>>>> >>> impalad binary and libfesupport.so under sbin-retail or sbin-debug
>>>> for the
>>>> >>> release or debug builds respectively. You also need to replace
>>>> >>> impala-frontend-*.jar and impala-data-source-api*.jar.
>>>> >>>
>>>> >>> You also need to make sure the statestored and catalogd symlinks
>>>> point to
>>>> >>> the impalad binary,
>>>> >>>
>>>> >>> On Mon, Sep 12, 2016 at 1:06 PM, Pradeep Nayak <
>>>> pradeep1288@gmail.com>
>>>> >>> wrote:
>>>> >>>
>>>> >>>> This question may sound noob, but apologies in advance.
>>>> >>>>
>>>> >>>> I have changes in the impala source code (both backend and
frontend
>>>> >>>> components). How do I go about installing this version of
Impala
>>>> on my
>>>> >>>> cloudera test cluster ? I know the path where I can replace
the
>>>> front end
>>>> >>>> built jar file, but not sure of the backend parts.
>>>> >>>>
>>>> >>>> Regards,
>>>> >>>> Pradeep Nayak
>>>> >>>>
>>>> >>>> http://pradeepnayak.in
>>>> >>>> http://twitter.com/_prdp
>>>> >>>>
>>>> >>>
>>>> >>>
>>>> >>
>>>>
>>>
>>>
>>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message