Hi Quanlong, If you dont need full debuginfo on your cluster, you might consider running 'strip --strip-debug' on the impalad binary that you output. Between that and using 'rsync' instead of copying a new full directory of jars every time, it's usually not that many MB (<100?) I usually do builds on a machine in the same network as the machines I plan on deploying on so that the copy runs at several hundred MB/second, rather than building on my laptop far away.
Tools like pscp and pssh are also handy of course. Hope that helps, -Todd On Wed, Apr 25, 2018 at 1:48 AM, Quanlong Huang <[email protected]> wrote: > Hi all, > > > Recently when I have a try on Impala-2.12.0-rc1, I find it really hard to > deploy Impala manually (I used to do this by Cloudera Manager). The > directory size is huge after compiled so I only distributed something I > thought really needed. This work is tedious and prone to errors. > > > Is there a best practice for packaging and distributing the binaries after > compiling? > > > Thanks, > Quanlong -- Todd Lipcon Software Engineer, Cloudera
