[jira] [Commented] (KUDU-1334) Support pid_max > 16 bits in the mini cluster

["Manukranth Kolloju (JIRA)" <ji...@apache.org>]

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

Manukranth Kolloju commented on KUDU-1334:
------------------------------------------

Looks like the flexible 127.x.x.x loopback address range in ipv4 has been brought down to one ipv6 address ::1/128
Are there plans to make this mini cluster work with ipv6 bind addresses? 

> Support pid_max > 16 bits in the mini cluster
> ---------------------------------------------
>
>                 Key: KUDU-1334
>                 URL: https://issues.apache.org/jira/browse/KUDU-1334
>             Project: Kudu
>          Issue Type: Improvement
>          Components: test
>    Affects Versions: 0.5.0
>            Reporter: Jean-Daniel Cryans
>
> Pretty much anybody running on newer machines/platforms will hit this while running the unit tests:
> {noformat}
> 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: ***
> {noformat}
> Having this limitation was fine but now it's something everybody hits.
> The workaround is running this:
> {noformat}
> echo "32768" > /proc/sys/kernel/pid_max
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)