Uploaded image for project: 'Phoenix'
  1. Phoenix
  2. PHOENIX-4736

PQS statement and connection metrics handling

    XMLWordPrintableJSON

Details

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

    Description

      Phoenix fat client exposes a number of metrics at StatementLevel as well as ConnectionLevel. PQS uses avatica server and exposes two metrics at this point of time, which is request end to end time and request serialization/deserialization time. These metrics are not super useful for PQS operations POV, however we need them to track the bad client and mis-usage.

      This Jira is to discuss how we should handle those metrics. 

      1. As pointed by jamestaylor, we can use SYSTEM.LOG table as a potential option here. 

      2. Write a shim layer to convert the metrics to hbase-metrics, which internally uses hadoop-metrics2 and define fine sink as the output.

      Additional ideas welcome.

      elserj apurtell tdsilva 

      Attachments

        Activity

          People

            Unassigned Unassigned
            karanmehta93 Karan Mehta
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated: