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

S2S initial connection behavior enhancement

Agile BoardAttach filesAttach ScreenshotVotersStop watchingWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • None
    • Core Framework, Core UI
    • None

    Description

      s2s client behavior and initial connection improvement is needed.
      Current experience is this: I, as a client (e.g. minifi), connect to a nifi cluster of e.g. 10 nodes. but i need to specify 1 node URL to establish this connection. this node may not be available 100% and go down, in which case my initial connection won't work.
      Once S2S makes the first connection, it then has a list of all nodes, and can check their status. But first connection failure would be a concern if the specified URL is somehow not working. Usually for these problems, the client should be able to specify multiple urls (according to multiple target cluster nodes), comma-separated.

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            ijokarumawak Koji Kawamura
            ijokarumawak Koji Kawamura
            Votes:
            0 Vote for this issue
            Watchers:
            3 Stop watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment