[
https://issues.apache.org/jira/browse/KUDU-1334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16884240#comment-16884240
]
Alexey Serbin commented on KUDU-1334:
-------------------------------------
Ah, I see. I haven't looked at IPv6 yet. Probably, using some sort of
workaround you mentioned for loopback interfaces should be fine. However, I
wouldn't be surprised if it were necessary to manually add/configure IPv6
addresses for loopbacks if using one of those approaches.
If you are constrained with the limitation of 18 bits for maximum PID, another
possible solution might be not using {{UNIQUE_LOOPBACK}} mode, but that would
limit the concurrency while running the tests to avoid conflicts (you can see
how it's done in case of macOS). That's not the end of the world, but if you
hit the necessity to configure 'local' IPv6 addresses for network interfaces
anyways, instead of adding/removing addresses (under super-user creds) you
might consider switching to other than UNIQUE_LOOPBACK modes. Ideally, it
would be nice to have UNIQUE_LOOPBACK mode working in IPv6 case on Linux as
well, but at this point I don't know whether it's possible at all.
Anyway, thank you for your work on KUDU-1457 !
> 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
> Assignee: Alexey Serbin
> Priority: Major
> Fix For: 1.6.0
>
>
> 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
(v7.6.14#76016)
