[HADOOP-8499] Lower min.user.id to 500 for the tests

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.0.0-alpha
• Fix Version/s: 2.0.2-alpha
• Hadoop Flags: Reviewed
• Assignee: Colin McCabe
• Reporter: Colin McCabe
• Created: 08/Jun/12 22:37
• Updated: 11/Oct/12 17:45
• Resolved: 13/Jul/12 23:05

Description

On Linux platforms where user IDs start at 500 rather than 1000, the build currently is broken. This includes CentOS, RHEL, Fedora, SuSE, and probably most other Linux platforms. It does happen to work on Debian and Ubuntu, which explains why Jenkins hasn't caught it yet.

Other users will see something like this:

[INFO] Requested user cmccabe has id 500, which is below the minimum allowed 1000
[INFO] FAIL: test-container-executor
[INFO] ================================================
[INFO] 1 of 1 test failed
[INFO] Please report to [e-mail]
[INFO] ================================================
[INFO] make[1]: *** [check-TESTS] Error 1
[INFO] make[1]: Leaving directory `/home/cmccabe/hadoop4/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn
-server/hadoop-yarn-server-nodemanager/target/native/container-executor'

And then the build fails. Since native unit tests are currently unskippable (HADOOP-8480) this makes the project unbuildable.

The easy solution to this is to relax the constraint for the unit test. Since the unit test already writes its own configuration file, we just need to change it there.

In general, I believe that it would make sense to change this to 500 across the board. I'm not aware of any Linuxes that create system users with IDs higher than or equal to 500. System user IDs tend to be below 200.

However, if we do nothing else, we should at least fix the build by relaxing the constraint for unit tests.

Issue Links

• is related to: MAPREDUCE-2376 test-task-controller fails if run as a userid < 1000
• is related to: HADOOP-8480 The native build should honor -DskipTests