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.conf
file into the/opt/mapr/conf/warden.conf
file. - For secure clusters: On all nodes, manually copy
/opt/mapr/conf.new/mapr.login.conf
to 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.conf
directory from the pre-6.0 release version to the/opt/mapr/apiserver/conf/properties.cfg
file of the upgraded release version.For example, the following from the
/opt/mapr/conf/web.conf
file from the pre-6.0 version must be manually copied over to the/opt/mapr/apiserver/conf/properties.cfg
file 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.conf
file with custom settings in/opt/mapr/conf/fuse.conf.backup
file and restart FUSE for the settings to take effect.After the upgrade, on all supported operating systems other than Ubuntu, the new
fuse.conf
file and a backup copy of thefuse.conf
file from prior version namedfuse.conf.backup
are available in the/opt/mapr/conf
directory. You can find the new parameters with default values in the newfuse.conf
file and your custom settings from the prior version in thefuse.conf.backup
file. On Ubuntu, you can find the newfuse.conf
file in the/opt/mapr/conf
directory and by default, there is no backup copy of thefuse.conf
file from prior version unless you created one before upgrade.