anchor.diff:  |====
   
   
  -*H2 Settings* +
  +==== H2 Settings
   
   The H2 Settings section defines the settings for the H2 database, which keeps track of user access and flow controller history.
   
  
positive.code: that should run the embedded ZooKeeper server. Generally, it is advisable to run ZooKeeper on either 3 or 5 nodes. Running on fewer than 3 nodes
  provides less durability in the face of failure. Running on more than 5 nodes generally produces more network traffic than is necessary. Additionally,
  running ZooKeeper on 4 nodes provides no more benefit than running on 3 nodes, ZooKeeper requires a majority of nodes be active in order to function.
  However, it is up to the administrator to determine the number of nodes most appropriate to the particular deployment of NiFi. An embedded ZooKeeper
  server cannot be run on the NCM.
  
  If the `nifi.state.management.embedded.zookeeper.start` property is set to `true`, the `nifi.state.management.embedded.zookeeper.properties` property
  in _nifi.properties_ also becomes relevant. This specifies the ZooKeeper properties file to use. At a minimum, this properties file needs to be populated
  
negative.code: |nifi.volatile.content.repository.block.size|The Content Repository block size. The default value is 32KB.
  |====
  
  ==== Provenance Repository
  
  The Provenance Repository contains the information related to Data Provenance. The next three sections are for Provenance Repository properties.
  
  