Client Side Operations Timeout GA

XMLWordPrintableJSON

    • Type: Epic
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: CSOT
    • None
    • CSOT GA
    • Java Drivers
    • None
    • Hide
      1. What would you like to communicate to the user about this feature?
      2. Would you like the user to see examples of the syntax and/or executable code and its output?
      3. Which versions of the driver/connector does this apply to?
      Show
      1. What would you like to communicate to the user about this feature? 2. Would you like the user to see examples of the syntax and/or executable code and its output? 3. Which versions of the driver/connector does this apply to?
    • In Progress
    • 18
    • 2
    • 0
    • 100
    • -88
    • None
    • Hide

      Engineer(s): Slav Babanin (Valentin Kavalenka, Ross Lawley)

      2025-07-18:

      • What was accomplished since the last update?
        • Fixed flaky OIDC Kubernetes tests caused by high RTT; raised a PR and closed the issue.
        • Completed investigation of the flaky MultiBatch_bulkWrites test. The issue was not in the transport layer (TlsChannelImpl), but in our async response handling logic - affecting not just CSOT but async I/O more broadly. Fixed the CSOT-specific bug and created follow-up tickets for broader improvements.
        • Began reviewing CSOT refactoring work handed off from Maxim Katcharov and started building on top of those changes across the rest of the codebase.
      • What's the focus over the next two weeks?
        • Get the bug fix PR for waitQueueTimeoutMS approved and merged.
        • Continue working on CSOT refactoring - coordinating with teammates at intermediate steps to evaluate whether the refactoring efforts are improving maintainability and clarity.
        • Review PR for JAVA-5579, raised by Nabil Hachicha.
      • Any risks/blockers/impediments?
        • Nothing.
      •  Anything else you think is worth highlighting to stakeholders? 

      2025-07-03:

      • What was accomplished since the last update?
        • Added CSOT support to OIDC; the PR was reviewed, approved, and merged.
        • Fixed a bug where waitQueueTimeoutMS was not ignored when timeoutMS was set. Raised a PR, which is currently under review.
        • Started investigating a flaky MultiBatch_bulkWrites test, suspected to be caused by a bug in our transport layer (TlsChannelImpl).
      • What's the focus over the next two weeks?
        • Get the bug fix PR for waitQueueTimeoutMS approved and merged.
        • Continue troubleshooting to identify the root cause of the transport layer issue.
        • Address flaky tests related to JAVA-5375, determining whether they are true bugs or just unstable tests that require retries or refactoring.
      • Any risks/blockers/impediments?
        • Nothing.
      •  Anything else you think is worth highlighting to stakeholders? 
      Show
      Engineer(s): Slav Babanin (Valentin Kavalenka, Ross Lawley) 2025-07-18: What was accomplished since the last update? Fixed flaky OIDC Kubernetes tests caused by high RTT; raised a PR and closed the issue. Completed investigation of the flaky MultiBatch_bulkWrites test. The issue was not in the transport layer (TlsChannelImpl), but in our async response handling logic - affecting not just CSOT but async I/O more broadly. Fixed the CSOT-specific bug and created follow-up tickets for broader improvements. Began reviewing CSOT refactoring work handed off from Maxim Katcharov and started building on top of those changes across the rest of the codebase. What's the focus over the next two weeks? Get the bug fix PR for waitQueueTimeoutMS approved and merged. Continue working on CSOT refactoring - coordinating with teammates at intermediate steps to evaluate whether the refactoring efforts are improving maintainability and clarity. Review PR for JAVA-5579 , raised by Nabil Hachicha . Any risks/blockers/impediments? Nothing.  Anything else you think is worth highlighting to stakeholders?  Two tickets from this epic are currently blocked on DRIVER tickets: JAVA-5069 blocked on DRIVERS-2884 . JAVA-5399 blocked on DRIVERS-2347 . 2025-07-03: What was accomplished since the last update? Added CSOT support to OIDC; the PR was reviewed, approved, and merged. Fixed a bug where waitQueueTimeoutMS was not ignored when timeoutMS was set. Raised a PR, which is currently under review. Started investigating a flaky MultiBatch_bulkWrites test, suspected to be caused by a bug in our transport layer (TlsChannelImpl). What's the focus over the next two weeks? Get the bug fix PR for waitQueueTimeoutMS approved and merged. Continue troubleshooting to identify the root cause of the transport layer issue. Address flaky tests related to JAVA-5375 , determining whether they are true bugs or just unstable tests that require retries or refactoring. Any risks/blockers/impediments? Nothing.  Anything else you think is worth highlighting to stakeholders?  Two tickets from this epic are currently blocked on DRIVER tickets: JAVA-5069 blocked on DRIVERS-2884 . JAVA-5399 blocked on DRIVERS-2347 .
    • 17.5
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Summary

      What is the problem or use case, what are we trying to achieve?

      Motivation

      Who is the affected end user?

      Who are the stakeholders?

      How does this affect the end user?

      Are they blocked? Are they annoyed? Are they confused?

      How likely is it that this problem or use case will occur?

      Main path? Edge case?

      If the problem does occur, what are the consequences and how severe are they?

      Minor annoyance at a log message? Performance concern? Outage/unavailability? Failover can't complete?

      Is this issue urgent?

      Does this ticket have a required timeline? What is it?

      Is this ticket required by a downstream team?

      Needed by e.g. Atlas, Shell, Compass?

      Is this ticket only for tests?

      Is this ticket have any functional impact, or is it just test improvements?

      Cast of Characters

      Engineering Lead:
      Document Author:
      POCers:
      Product Owner:
      Program Manager:
      Stakeholders:

      Channels & Docs

      Slack Channel

      [Scope Document|some.url]

      [Technical Design Document|some.url]

              Assignee:
              Slav Babanin
              Reporter:
              Tom Selander
              Ajay Tandon Ajay Tandon
              None
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                None
                None