Uploaded image for project: 'Data Management'
  1. Data Management
  2. DM-864

XXX Replace mysql-proxy with czar internal handling of mysql protocol

    Details

    • Type: Epic
    • Status: To Do
    • Resolution: Unresolved
    • Fix Version/s: None
    • Component/s: Qserv
    • Labels:
    • Templates:
    • Epic Name:
      mysql-proxy replacement
    • Team:
      Data Access and Database

      Description

      Currently mysql connection from clients is handled by mysql-proxy which passes queries to czar and returns query results back to user. This proxy-czar combination has some significant issues which limit what we can do with it:

      • very limited possibility to generate data on proxy side (it has to result from SQL query of some sort)
      • proxy has very little information about result data and cannot do transformations on that

      It looks like we can achieve better result if we can implement our own proxy which can work at the mysql wire-level protocol and integrate that proxy directly into czar. This would eliminate one server process from our current setup and should help both performance and stability.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                salnikov Andy Salnikov
                Reporter:
                salnikov Andy Salnikov
                Watchers:
                Andy Salnikov, Daniel Wang [X] (Inactive), Jacek Becla, John Swinbank, Kian-Tat Lim
              • Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:

                  Summary Panel