Step 2: Manually Update Configuration Files
After upgrading core using a manual offline or rolling upgrade method, update your configuration files.
To manually update the configuration files:
- On all nodes, manually merge new configuration settings from the
          
/opt/mapr/conf.new/warden.conffile into the/opt/mapr/conf/warden.conffile. - For secure clusters: On all nodes, manually copy
          
/opt/mapr/conf.new/mapr.login.confto the/opt/mapr/conf/directory, and set the file permissions to 0644. This file contains Zookeeper security information. - On all nodes, manually merge new configuration settings from the files in the
          
/opt/mapr/conf/conf.d.new/directory to the files in the/opt/mapr/conf/conf.d/ directory. - Manually merge the port and authentication configuration information in the
          
/opt/mapr/conf/web.confdirectory from the pre-6.0 release version to the/opt/mapr/apiserver/conf/properties.cfgfile of the upgraded release version.For example, the following from the
/opt/mapr/conf/web.conffile from the pre-6.0 version must be manually copied over to the/opt/mapr/apiserver/conf/properties.cfgfile of the new version:# HTTPS Settings mapr.webui.https.port=8443 mapr.rest.auth.methods=kerberos,basic // if kerberos auth - Manually merge new configuration settings in 
/opt/mapr/conf/fuse.conffile with custom settings in/opt/mapr/conf/fuse.conf.backupfile and restart FUSE for the settings to take effect.After the upgrade, on all supported operating systems other than Ubuntu, the new
fuse.conffile and a backup copy of thefuse.conffile from prior version namedfuse.conf.backupare available in the/opt/mapr/confdirectory. You can find the new parameters with default values in the newfuse.conffile and your custom settings from the prior version in thefuse.conf.backupfile. On Ubuntu, you can find the newfuse.conffile in the/opt/mapr/confdirectory and by default, there is no backup copy of thefuse.conffile from prior version unless you created one before upgrade.