FWIW, I've tried 16.04 XFCE / Ubuntu studio variants on two different HW machines now, was able to build impala on one and load data, but both machines flaked out with weird graphics related failures after kernel upgrades resulting in a black screen on boot. I was able to debug one of them enough to get it running again and also enough to know I didn't want to repeat the procedure, so I upgraded to 17.04 and have a somewhat working system, but I'd recommend avoiding any customization of packages and installs unless you enjoy headless debugging, and I'd recommend avoiding 17.04 entirely if you want a stable supported base.
- Zach On Sun, May 21, 2017 at 11:13 AM, Jim Apple <[email protected]> wrote: > I was able to run all the data loading and all of the core tests. One > Kudu test flaked a couple of times on a timeout error. > > On Sun, May 21, 2017 at 10:10 AM, Tim Armstrong <[email protected]> > wrote: > > Did you manage to run all of the tests and data loading? I remember a > while > > back I was having issues with Kudu crashing - never retried to see if it > > got better. > > > > On Sat, May 20, 2017 at 9:23 PM, Jim Apple <[email protected]> wrote: > > > >> I am hoping to upgrade from Ubuntu 14.04 to 16.04. In order to check > >> that I could still do Impala development work, I bootstrapped a > >> development environment on a 16.04 cloud instance. The script that > >> worked for me is here: > >> > >> https://cwiki.apache.org/confluence/display/IMPALA/Bootstrap > >> ping+an+Impala+Development+Environment+From+Scratch > >> > >> While it might be useful to have this as a Jenkins job, I have no > >> plans to create such a job. > >> > >> It might be a bit cleaner to get this done in the chef repo in > >> https://github.com/awleblang/impala-setup, but I don't plan to do that > >> at this time. > >> >
