[ 
https://issues.apache.org/jira/browse/IMPALA-9566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17071263#comment-17071263
 ] 

ASF subversion and git services commented on IMPALA-9566:
---------------------------------------------------------

Commit 5bdd3adb1aef9729a122d57490fefb521eef8885 in impala's branch 
refs/heads/master from Fang-Yu Rao
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=5bdd3ad ]

IMPALA-9566: Sentry service should not be started after IMPALA-8870

Due to the incompatibility between different versions of the Guava
libraries, after bumping up Guava in IMPALA-8870, our build script is
not supposed to start up the Sentry service when starting the
minicluster because Sentry has not had its Guava bumped up yet. However,
the patch for IMPALA-8870 did not take this into consideration when
$TARGET_FILESYSTEM is s3 and thus run-all.sh still attempts to start
up Sentry in this case. This patch fixes the bug.

Testing:
- Verified that this patch passes the core tests in the DEBUG build when
  $TARGET_FILESYSTEM is s3.

Change-Id: If81846f4251fb2aa752ba8c33615cae0ab513a62
Reviewed-on: http://gerrit.cloudera.org:8080/15590
Reviewed-by: Impala Public Jenkins <[email protected]>
Reviewed-by: Csaba Ringhofer <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>


> Sentry service should not be started after IMPALA-8870
> ------------------------------------------------------
>
>                 Key: IMPALA-9566
>                 URL: https://issues.apache.org/jira/browse/IMPALA-9566
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Frontend, Infrastructure
>            Reporter: Fang-Yu Rao
>            Assignee: Fang-Yu Rao
>            Priority: Major
>              Labels: broken-build
>
> Due to the incompatibility between different versions of the Guava libraries. 
> After bumping up Guava in IMPALA-8870, our build script is not supposed to 
> start up the Sentry service because Sentry does not have its Guava bumped up 
> yet.
> To fix this, when starting the underlying services, we should take into 
> consideration the case when {{$\{DEFAULT_FS}}} is neither 
> "{{hdfs://${INTERNAL_LISTEN_HOST}:20500}}" nor "{{${LOCAL_FS}}}". 
> Specifically, we should not attempt to start the Sentry server in the 
> following case.
> [https://github.com/apache/impala/blob/master/testdata/bin/run-all.sh#L102-L104]
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to