Uploaded image for project: 'ZooKeeper'
  1. ZooKeeper
  2. ZOOKEEPER-1239

add logging/stats to identify fsync stalls

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.3.4, 3.4.0, 3.5.0
    • Component/s: server
    • Labels:
      None
    • Release Note:
      committed to 3.3.4, 3.4, trunk rev 1202360

      Description

      We don't have any logging to identify fsync stalls. It's a somewhat common occurrence (after gc/swap issues) when trying to diagnose pipeline stalls - where outstanding requests start piling up and operational latency increases.

      We should have some sort of logging around this. e.g. if the fsync time exceeds some limit then log a warning, something like that.

      It would also be useful to publish "stat" information related to this. min/avg/max latency for fsync.

      This should also be exposed through JMX.

        Attachments

        1. ZOOKEEPER-1239_br34.patch
          3 kB
          Patrick Hunt
        2. ZOOKEEPER-1239_br33.patch
          3 kB
          Patrick Hunt

          Activity

            People

            • Assignee:
              phunt Patrick Hunt
              Reporter:
              phunt Patrick Hunt
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: