Skip to content
代码片段 群组 项目
  1. 8月 23, 2022
  2. 8月 20, 2022
  3. 8月 19, 2022
  4. 8月 18, 2022
  5. 8月 17, 2022
    • David Mao's avatar
      KCFUN-166: Reduce tenant sensor expiration (#7130) · 49561479
      David Mao 创作于
      7d expiration is a pretty long time to expire inactive metrics and impacts our datadog/druid bill apparently. This PR reduces the expiration to 1h. 
      
      Connection count sensors are exempted because we should technically only expire connection count metrics if the count is 0. We can fix this in a subsequent patch - possibly by using something like a CounterGaugeSuite to record all active connection counts that need metrics.
      49561479
    • Rajini Sivaram's avatar
      KGLOBAL-1958: Fix regression in updating corrupted cluster link configs (#7165) · c7ba2b7d
      Rajini Sivaram 创作于
      Reviewers: Sanjana Kaundinya <skaundinya@confluent.io>
      c7ba2b7d
    • k-raina's avatar
      KSECURITY-155: Add Request_Id, Connection_Id to correlate with... · 39690a51
      k-raina 创作于
      KSECURITY-155: Add Request_Id, Connection_Id to correlate with Authorization/Authentication/Request Audit Events (#6855)
      
      39690a51
    • Vikas Singh's avatar
      KAFKALESS-830: Add follower fetch rate at broker level (#7031) · 04cbdfda
      Vikas Singh 创作于
      As part of PR #6959 we added a fetch rate metric from the follower
      perspective so that we can see how much load is generated on the
      follower node because of replication. This PR adds that to the list of
      topic metrics that we use to aggregate and get corresponding broker
      metrics.
      
      Also did a minor refactoring to flip loops, making inner loop outer and
      outer loop inner as that was matching more to what the code was doing.
      04cbdfda
    • Vikas Singh's avatar
      KAFKALESS-830: Set replication bytes in/out for topics (#7023) · 9317be02
      Vikas Singh 创作于
      * KAFKALESS-830: Set replication bytes in/out for topics
      
      This change updates the replication bytes in/out at the topic level. For
      the replication bytes out, it makes it same as the bytes-in for the
      topic. For the replication bytes in, it goes over leader of all
      followers of a topic on a broker and sets it as sum of all leader
      bytes-in.
      
      A follow up PR will do similar change at broker level.
      
      Couple of name refactoring was made in the Cluster class that made this
      PR bigger than the small change it contains. I have also added new tests
      to make sure that replication bytes in/out calculation is done correctly
      both for cases where all metrics are present as well as when metrics are
      missing.
      9317be02
    • David's avatar
      a50fbcbc
    • Akhilesh C's avatar
      KGLOBAL-1867: Fix the NPE exception in isAutoMirrorTopic() check when the link is failed (#7139) · 3b749f46
      Akhilesh C 创作于
      * KGLOBAL-1867: Fix the NPE exception in isAutoMirrorTopic() check when the link is failed
      
      When the link fails, we set the config to null. We're not handling this
      correctly in isAutoMirrorTopic() check which relies on config to understand if
      a mirror topic is auto-mirrored. This solution is to simply default the
      behavior of the check to false when the link is failed. This way we might let
      the customer delete some auto-mirror topics when the link is in the failed state. But
      when the link comes back, we'll mirror the topic again. Another approach is to
      not let customers delete a topic when the link is failed and we're not able to use
      the config to determine if the topic is auto-mirrored. The restriction is much
      bigger here and is not the behavior intended for a failed link.
      3b749f46
    • Anastasia Vela's avatar
    • Rajini Sivaram's avatar
      KGLOBAL-1952: Attempt to shutdown both clusters in CL tests even if one fails... · c46e6200
      Rajini Sivaram 创作于
      KGLOBAL-1952: Attempt to shutdown both clusters in CL tests even if one fails to avoid thread leak impacting other tests (#7144)
      
      * KGLOBAL-1952: Attempt to shutdown both clusters in CL tests even if one fails to avoid thread leak impacting other tests
      c46e6200
  6. 8月 16, 2022
加载中