This is an automated email from the ASF dual-hosted git repository.
phrocker pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/nifi-minifi-cpp.git
The following commit(s) were added to refs/heads/master by this push:
new 81eb50a MINIFICPP-853: Minor updates to readmes
81eb50a is described below
commit 81eb50a333f42049af5e2636c392f41bc9e1b3f6
Author: Marc Parisi <[email protected]>
AuthorDate: Wed May 22 06:40:23 2019 -0400
MINIFICPP-853: Minor updates to readmes
This closes #566.
Approved on GH by arpadboda.
Signed-off-by: Marc Parisi <[email protected]>
---
CONFIGURE.md | 7 ++++---
OPS.md | 8 +++++---
2 files changed, 9 insertions(+), 6 deletions(-)
diff --git a/CONFIGURE.md b/CONFIGURE.md
index f4151b6..bf76ce3 100644
--- a/CONFIGURE.md
+++ b/CONFIGURE.md
@@ -298,9 +298,10 @@ The MQTTController Service can be configured for MQTT
connectivity and provide t
In the configuration below there are two classes defined under
"NetworkPrioritizerService", one class "NetworkPrioritizerService2" defines
en0, and en1.
If en0 is down at any point, then en1 will be given priority before
resorting to en2 and en3 of "NetworkPrioritizerService3". If the throughput
for
"NetworkPrioritizerService2" exceeds the defined throughput or the max
payload of 1024, then "NetworkPrioritizerService3" will be used. If Max Payload
and
- Max Throughput are not defined, then they will not be limiting factors. As
of release, 0.5.0, Max Payload will only be used for processors that custom
- implement that feature. RPGs will not support max payloads until 0.6.0.
Additionally, since connection queues aren't prioritized, you must have a live
connection
- for your data to send it. Since connection queues can't be re-prioritized,
this can create a starvation problem. The configuration is required to account
for this.
+ Max Throughput are not defined, then they will not be limiting factors.
+
+ Since connection queues can't be re-prioritized, this can create a
starvation problem if no connection is available.
+ The configuration is required to account for this.
Controller Services:
- name: NetworkPrioritizerService
diff --git a/OPS.md b/OPS.md
index 923de64..9cce9f5 100644
--- a/OPS.md
+++ b/OPS.md
@@ -26,13 +26,15 @@ This readme defines operational commands for managing
instances.
## Description
-Apache NiFi MiNiFi C++ can be managed through our [C2
protocol](https://cwiki.apache.org/confluence/display/MINIFI/C2+Design+Proposal)
+Apache NiFi MiNiFi C++ can be managed through our [C2
protocol](https://cwiki.apache.org/confluence/display/MINIFI/C2+Design)
or through a local interface called the MiNiFi Controller. This feature is
disabled by default, and requires that C2 be enabled
-and configured with an agent class before using the MiNiFi controller features
outlined here.
+and configured with an agent class before using the MiNiFi controller features
outlined here. MiNiFi controller is an example
+implementation of our C2 protocol. This featureset is not intended to replace
your Command and Control implementation. Instead
+it is meant to provide testing and minimal operational capabilities by
example.
## Managing MiNiFi
-The MiNiFi controller is an executable in the bin directory that can be used
to control the MiNiFi C++ agent while it runs -- utilizing the [Command and
Control
Protocol](https://cwiki.apache.org/confluence/display/MINIFI/C2+Design+Proposal).
Currently the controller will let you stop subcomponents within a running
instance, clear queues, get the status of queues, and update the flow for a
warm re-deploy.
+The MiNiFi controller is an executable in the bin directory that can be used
to control the MiNiFi C++ agent while it runs -- utilizing the [Command and
Control
Protocol](https://cwiki.apache.org/confluence/display/MINIFI/C2+Design).
Currently the controller will let you stop subcomponents within a running
instance, clear queues, get the status of queues, and update the flow for a
warm re-deploy.
The minificontroller can track a single MiNiFi C++ agent through the use of
three options. Port is required.
The hostname is not and will default to localhost. Additionally,
controller.socket.local.any.interface allows
