On Tue, Feb 16, 2016 at 11:58 AM, Stack <[email protected]> wrote: > On Tue, Feb 16, 2016 at 11:33 AM, Jean-Daniel Cryans <[email protected]> > wrote: > > > On Tue, Feb 16, 2016 at 11:30 AM, Stack <[email protected]> wrote: > > > > > On Tue, Feb 16, 2016 at 10:46 AM, Jean-Daniel Cryans < > > [email protected]> > > > wrote: > > > > > > > On Tue, Feb 16, 2016 at 10:37 AM, Stack <[email protected]> wrote: > > > > > > > > > On Tue, Feb 16, 2016 at 9:25 AM, Jean-Daniel Cryans < > > > [email protected] > > > > > > > > > > wrote: > > > > > > > > > > > > > > .... > > > > > To get so many is likely something important missing. My guess would be > > NTP. Checkout the troubleshooting guide if that's the case. > > > > > > > NTP is installed. > > Looking in logs for one of the failed tests (JD) found: > > ... > I0216 11:27:23.617383 110702 external_mini_cluster.cc:582] Started > /home/stack/apache-kudu-incubating-0.7.0/build/rc/bin/kudu-master as pid > 110706 > F0216 11:27:23.617473 110702 external_mini_cluster.cc:258] Check failed: p > <= MathLimits<uint16_t>::kMax (110702 vs. 65535) Cannot run on systems with > >16-bit pid > *** Check failure stack trace: *** >
Oh yeah that's a limitation in the unit tests, basically anything that uses the minicluster will fail. I opened https://issues.cloudera.org/browse/KUDU-1334 The fix is: echo "32768" > /proc/sys/kernel/pid_max
