[
https://issues.apache.org/jira/browse/IMPALA-10016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17219942#comment-17219942
]
ASF subversion and git services commented on IMPALA-10016:
----------------------------------------------------------
Commit cfa8a7a5e54fe7826945f688df03eabc3cd03dd4 in impala's branch
refs/heads/master from Joe McDonnell
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=cfa8a7a ]
IMPALA-10278: Use full libraries for impalad_executor Docker container
This backs out the piece of IMPALA-10016 that used a pared-down
set of libraries for the impalad_executor. That pared-down
set was missing org.apache.impala.common.JniUtil, which
prevented the impalad_executor container from starting up.
Testing:
- Ran a docker core job with one coord_exec and two executors
and it was able to startup where it wouldn't before
Change-Id: Ieecca61cd3c11f446b922a04fdeb5fd0c90fc971
Reviewed-on: http://gerrit.cloudera.org:8080/16640
Reviewed-by: Tim Armstrong <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
> Split jars for Impala executor and coordinator Docker images
> ------------------------------------------------------------
>
> Key: IMPALA-10016
> URL: https://issues.apache.org/jira/browse/IMPALA-10016
> Project: IMPALA
> Issue Type: Sub-task
> Reporter: Sahil Takiar
> Assignee: Sahil Takiar
> Priority: Major
> Fix For: Impala 4.0
>
>
> Impala executors and coordinator currently have a common base images. The
> base image defines a set of jar files needed by either the coordinator or the
> executor. In order to reduce the image size, we should split out the jars
> into two categories: those necessary for the coordinator and those necessary
> for the executor. This should help reduce overall image size.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]