joewitt commented on a change in pull request #3923: NIFI-6866 Created the RocksDBComponentStatusRepository to persist com… URL: https://github.com/apache/nifi/pull/3923#discussion_r366557945
########## File path: nifi-docs/src/main/asciidoc/administration-guide.adoc ########## @@ -2895,13 +2895,31 @@ configure two days worth of historical data with a data point snapshot occurring are 12 (60 / 5) snapshot windows for that time period. To keep that data for 48 hours (12 * 48) you end up with a buffer size of 576. +The following properties are applicable to all implementations of the Component Status Repository: + |==== |*Property*|*Description* -|`nifi.components.status.repository.implementation`|The Component Status Repository implementation. The default value is `org.apache.nifi.controller.status.history.VolatileComponentStatusRepository` and should not be changed. +|`nifi.components.status.repository.implementation`|The Component Status Repository implementation. The default value is `org.apache.nifi.controller.status.history.VolatileComponentStatusRepository`. The only other option at this time +is `org.apache.nifi.controller.status.history.RocksDBComponentStatusRepository` |`nifi.components.status.repository.buffer.size`|Specifies the buffer size for the Component Status Repository. The default value is `1440`. |`nifi.components.status.snapshot.frequency`|This value indicates how often to present a snapshot of the components' status history. The default value is `1 min`. |==== +=== Volatile Component Status Repository + +The default implementation of a Component Status Repository. This implementation keeps the configured amount of history in memory as long as NiFi is running. + +=== RocksDB Component Status Repository + +The RocksDB Component Status Repository is a new implementation which has thus far only been built and tested in a Centos 7 environment. Review comment: Do you have reason to believe it might work on other platforms? ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
