Uploaded image for project: 'Ignite'
  1. Ignite
  2. IGNITE-3480

Use single TCP port per node

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Open
    • Major
    • Resolution: Unresolved
    • None
    • None
    • None

    Description

      Currently we have several network components and each of them starts their own TCP server and occupies separate port.

      What if we use only 1 port per node and dispatch discovery, communication, rest, time server, etc traffic to proper component?

      Goals:

      • simplify deployment procedure
      • lower resource requirements (less ports, probably, less connections, etc).
      • make network IO related code consistent
      • fully move it to NIO APIs (discovery uses blocking IO and thread-per connection model).

      Attachments

        Activity

          People

            yzhdanov Yakov Zhdanov
            yzhdanov Yakov Zhdanov
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: