On Tue, 21 Jun 2011 06:37:50 -0700, Alex Kozlov <ale...@cloudera.com> wrote: > However, the job's tasks are executed in a separate JVM and some > of the parameters, like max heap from *mapred.java.child.opts*, are set > during the job execution. In this case the parameter is coming from the > client side where the whole configuration is serialized and passed to the > slave TT nodes. It is never read from the TT node's *-site.xml. I don't > know a comprehensive list of parameters that can be changed by the client > side, but most of the parameters are set during the daemon startup.
mapred.java.child.opts was the one that led one of us to believe that changes in mapred-site.xml take effect for all newly-launched jobs. What about keep.failed.task.files? Do you know if that one needs a restart of JT or TTs?
