Uploaded image for project: 'Ignite'
  1. Ignite
  2. IGNITE-22086

Thin 3.0: observableTimestamp is 0 after handshake

    XMLWordPrintableJSON

Details

    Description

      We propagate observableTimestamp to client with every response (see ClientInboundMessageHandler#writeResponseHeader), but not on handshake. As a result, the very first operation from the client has observableTimestamp=0, which can lead to causality issues.

      Attachments

        Issue Links

          blocks

          Bug - A problem which impairs or prevents the functions of the product. IGNITE-22068 Inconsistent SQL and Criteria API behaviour

          • Major - Major loss of function.
          • Open
          links to

          Web Link GitHub Pull Request #3679

          Activity

            People

              ptupitsyn Pavel Tupitsyn
              ptupitsyn Pavel Tupitsyn
              Igor Sapego Igor Sapego
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 40m
                  40m