Uploaded image for project: 'Tajo'
  1. Tajo
  2. TAJO-1228

TajoClient should communicate with only TajoMaster without TajoWorker

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 0.10.0
    • Component/s: Java Client
    • Labels:
      None

      Description

      Currently, TajoClient connects with TajoMaster as well as TajoWorker. A query submission is passed from TajoClient to TajoMaster, and than TajoMaster forwards the query to one query master running on a TajoWorker. After than, a client monitors the query progress through the query master.

      In other words, TajoClient contacts both TajoMaster and TajoWorker. It has three disadvantages:

      • a network firewall should allow connections to TajoWorker nodes.
      • all components should have complex states and communication logic one another.
      • TAJO-1160 is trying to remove hadoop dependency from TajoClient. In TAJO-1160, TajoClient will use only some server which forwards query results to itself instead of reading directly HDFS. TajoMaster would be the best component to forward the query results because TajoClient always connects with TajoMaster. So, if TajoClient communicates with only TajoMaster, all client logic and protocol would be simple.

        Attachments

        1. TAJO-1228_4.patch
          35 kB
          Hyunsik Choi
        2. TAJO-1228_3.patch
          33 kB
          Hyunsik Choi
        3. TAJO-1228_2.patch
          52 kB
          Hyunsik Choi
        4. TAJO-1228.patch
          34 kB
          Hyunsik Choi

          Issue Links

            Activity

              People

              • Assignee:
                hyunsik Hyunsik Choi
                Reporter:
                hyunsik Hyunsik Choi
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: