[jira] [Commented] (IMPALA-8425) Evaluate size of Impala docker containers

["Joe McDonnell (JIRA)" <ji...@apache.org>]

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

Joe McDonnell commented on IMPALA-8425:
---------------------------------------

First pass:
 # The containers as they are include impalad, statestored, and catalogd. In a normal environment, these are all linked into a single executable with statestored and catalogd symlinked to impalad with special logic in main(). My guess is that the current containers don't do this, so this would cut out about 850MB.
 # My IMPALA_KUDU_HOME contains 1.1GB of stuff, and I think we don't need most of it. The executables in release/bin and release/sbin (each with a copy of kudu-master and kudu-tserver) should not be necessary. That cuts out about 1GB.

A recent run of the docker tests had this line:
Sending build context to Docker daemon  2.511GB

> Evaluate size of Impala docker containers
> -----------------------------------------
>
>                 Key: IMPALA-8425
>                 URL: https://issues.apache.org/jira/browse/IMPALA-8425
>             Project: IMPALA
>          Issue Type: Sub-task
>          Components: Infrastructure
>            Reporter: Tim Armstrong
>            Assignee: Joe McDonnell
>            Priority: Major
>
> We should take a look at the size of the containers produced by the build and see if it is worth optimising. I think the main contributor to size right now is likely the impala binary, which we could shrink by stripping debug symbols. We could also look at using a different base image from Ubuntu.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org