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

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

Commit 45c5652b6694864afef2af3fdf93d3bd8dfa7190 in impala's branch 
refs/heads/master from Tim Armstrong
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=45c5652 ]

IMPALA-8425: part 1: reduce size of binaries in container

* Symlink impalad/catalog/statestored inside container.
  This doesn't seem to really save any space - there's
  some kind of deduplication going on.
* Don't include libfesupport.so, which shouldn't be needed.
* strip debug symbols from the binary.
* Only include the libkuduclient.so libraries for Kudu

This shaves ~1.1GB from the image size- 250MB as a result
of the impalad binary changes and the remainder from the
Kudu changs.

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


> 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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to