Out-of-band configuration modifications are not supported. The service’s core responsibility is to deploy and maintain the service with a specified configuration. In order to do this, the service assumes that it has ownership of task configuration. If an end-user makes modifications to individual tasks through out-of-band configuration operations, the service will override those modifications at a later time. For example:
- If a task crashes, it will be restarted with the configuration known to the Scheduler, not one modified out-of-band.
- If a configuration update is initiated, all out-of-band modifications will be overwritten during the rolling update.
To prevent accidental data loss, the service does not support reducing the number of pods.
To prevent accidental data loss from reallocation, the service does not support changing volume requirements after initial deployment.
If your cluster doesn’t have enough resources to deploy the service as requested, the initial deployment will not complete until either those resources are available or until you reinstall the service with corrected resource requirements. Similarly, scale-outs following initial deployment will not complete if the cluster doesn’t have the needed available resources to complete the scale-out.
When the service is deployed on a virtual network, the service may not be switched to host networking without a full re-installation. The same is true for attempting to switch from host to virtual networking.
Task Environment Variables
Each service task has some number of environment variables, which are used to configure the task. These environment variables are set by the service Scheduler. While it is possible to use these environment variables in adhoc scripts (e.g. via
dcos task exec), the name of a given environment variable may change between versions of a service and should not be considered a public API of the service.
The “disk” configuration value is denominated in MB. We recommend that you set the configuration value
log_retention_bytes to a value smaller than the indicated “disk” configuration. See the Configuring section for instructions for customizing these values.
Legacy User Support
Legacy Authorized Users File is not supported.
LDAP Integration, OpenID Connect and Apache Knox
LDAP integration, OpenID Connect and Apache Knox are not supported.
The minimum memory requirement for NiFi installation is 512MB. NiFi installation will take time since the NiFi application is heavy in size (approx 1.10GB). The approximate installation time required would be around 20~25 Minutes for a 2 Node Cluster.