Uploaded image for project: 'Apache NiFi'
  1. Apache NiFi
  2. NIFI-5464

Local Ports are able to be started without incoming connections, then use a lot of CPU

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 1.10.0
    • Core Framework
    • None

    Description

      Currently, validation of a LocalPort simply checks that it has an outgoing connection. This means that it's possible to create an outgoing connection for a port but not have any incoming connections. When this happens, if the Port is started, the framework determines that it is a "source component" because it has no incoming connections. As such, it is never yielded via the "bored yield duration". This results in high CPU usage.

      The fix in this case, I believe, is to address the validation. We should not allow a Local Port to be enabled if it has no incoming connections.

      Attachments

        Issue Links

          Activity

            People

              markap14 Mark Payne
              markap14 Mark Payne
              Votes:
              1 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 0.5h
                  0.5h