[
https://issues.apache.org/jira/browse/MINIFICPP-374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16329530#comment-16329530
]
ASF GitHub Bot commented on MINIFICPP-374:
------------------------------------------
Github user phrocker commented on a diff in the pull request:
https://github.com/apache/nifi-minifi-cpp/pull/242#discussion_r162190115
--- Diff: README.md ---
@@ -609,6 +609,21 @@ Additionally, a unique hexadecimal
uid.minifi.device.segment should be assigned
class: ControllerServiceClass
Properties:
+### Linux Power Manager Controller Service
+ The linux power manager controller service can be configured to monitor
the battery level and status ( discharging or charging ) via the following
configuration.
+ Simply provide the capacity path and status path along with your
threshold for the trigger and low battery alarm and you can monitor your
battery and throttle
+ the threadpools within MiNiFi C++. Note that the name is identified must
be ThreadPoolManager.
+
+ Controller Services:
+ - name: ThreadPoolManager
+ id: 2438e3c8-015a-1000-79ca-83af40ec1888
+ class: LinuxPowerManagerService
+ Properties:
+ Battery Capacity Path: /path/to/battery/capacity
+ Battery Status Path: /path/to/battery/status
--- End diff --
Controller services provide a shared service. In this case the evaluation
of information to make a determination of whether or not we should reduce
threads. It has been discussed that we can move gathering of this information
into a Processor, but then we have to transfer it somewhere. In that flow we
need to build logic and feed that to elements such as the thread executor,
power management, etc. We would need to create a pipeline of logic that flows
beyond the processors into structural elements of MiNiFi C++. This is better
suited for a controller service. Controller services, by way of the
ControllerServiceProvider, are already designed to be part of the thread pools
( scheduling agents ) amongst other structural components.
This allows a single shared state to make an informed decision. While I can
see the case where we feed the controller service by way of the processor
output, we'd have to do so at the cost of incurring FlowFile management ( we
could have a single processor, but what's the point of that? ).
> Create thread management strategy through a controller service.
> ----------------------------------------------------------------
>
> Key: MINIFICPP-374
> URL: https://issues.apache.org/jira/browse/MINIFICPP-374
> Project: NiFi MiNiFi C++
> Issue Type: Improvement
> Reporter: marco polo
> Assignee: marco polo
> Priority: Major
>
> I've created a series of thread management strategy controller services. The
> first was a linux battery monitor that I'm contributing.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
