[
https://issues.apache.org/jira/browse/NIFI-11230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17719023#comment-17719023
]
ASF subversion and git services commented on NIFI-11230:
--------------------------------------------------------
Commit 436fd91a258320c0acf644d16c0f0fa7e16776bb in nifi's branch
refs/heads/main from Emilio Setiadarma
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=436fd91a25 ]
NIFI-11230 Added Runtime Configuration validation to nifi-bootstrap
This closes #7196
Co-authored-by: David Handermann <exceptionfact...@apache.org>
Signed-off-by: David Handermann <exceptionfact...@apache.org>
> Log Warnings on Startup for OS Best Practices
> ---------------------------------------------
>
> Key: NIFI-11230
> URL: https://issues.apache.org/jira/browse/NIFI-11230
> Project: Apache NiFi
> Issue Type: New Feature
> Reporter: David Handermann
> Assignee: Emilio Setiadarma
> Priority: Minor
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The Administrator's Guide outlines several [best
> practices|https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#configuration-best-practices]
> for optimal configuration of the Linux operating system to run NiFi.
> Not following these best practices can lead to confusing errors at runtime,
> such when NiFi does not have enough file handles or enough TCP sockets.
> Adding evaluation of these properties on startup and logging warnings for
> less-than-optimal settings would help avoid some runtime troubleshooting
> challenges.
> The initial implementation should cover the Linux platform, be should be
> designed using interfaces to gather the platform information, which would
> support extending similar checks to macOS.
> The implementation should check and warn for the following settings:
> # Maximum File Handles
> # Maximum Forked Processes
> # Maximum local TCP socket ports
> # Maximum TCP socket time wait interval
> # Swappiness enabled
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
