A while ago I've opened an issue related to this topic https://issues.apache.org/jira/browse/HADOOP-3287
My take is a little different, when submitting a job, the clients should only send to the jobtracker the configuration they explicitly set, then the job tracker would apply the defaults for all the other configuration. By doing this the cluster admin can modify things at any time and changes on default values take effect for all clients without having to distribute a new configuration to all clients. IMO, this approach was the intended behavior at some point, according to the Configuration.write(OutputStream) javadocs ' Writes non-default properties in this configuration.'. But as the write method is writing default properties this is not happening. This approach would also get rid of the separate mechanism (zookeeper, svn, etc) to keep clients synchronized as there would be no need to do so. Alejandro On Fri, May 16, 2008 at 10:25 PM, Ted Dunning <[EMAIL PROTECTED]> wrote: > > That is all that almost all of my arms-length clients need. With 18, all > clients should be able to ask for the default configuration if they have a > root URL which will make the amount of information needed for any and all > clients very small. > > > On 5/16/08 2:03 AM, "Steve Loughran" <[EMAIL PROTECTED]> wrote: > >> I agree. I think right now clients need a bit too much info about the >> name node; its URL should be all they need, and presumably who to log in >> as. > >
