Details
-
Improvement
-
Status: Open
-
Major
-
Resolution: Unresolved
-
0.22.0
-
None
-
None
Description
The taskcontroller.cfg configuration file seems unnecessary. It's parsed by the task-controller binary, and the path to it is baked into that binary at compile-time. It contains only 3 values, none of which are secret, all of which are also specified in either core-site.xml or mapred-site.xml. It seems like getting rid of taskcontroller.cfg will simplify configuration, and have no impact on the security of the system
I suggest we either:
- Pass these values as arguments to task-controller when we execute it.
- Use xerces to enable the task-controller to parse *-site.xml.
Of these two options, I think option 1 seems the cleanest/easiest. Either would be backward-compatible with existing configurations.