Uploaded image for project: 'Java Couchbase JVM Core'
  1. Java Couchbase JVM Core
  2. JVMCBC-1110

Client is not reliably removing itself from client records on shutdown

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Minor
    • 2.3.3
    • None
    • transactions
    • None
    • 1
    • SDK30

    Description

      Test

      7.0-stable Vs JAVA_SDK_MASTER / com.couchbase.transactions.cleanup.LostCleanupForSDKIntegrationTest.previouslyFailedTransactionIsCleanedUp_transactionCleanupConfigCollection

      is intermittently failing.  I've drilled in and it's because the performer has found an old client still registered in the client record.  The relevant logs are in this gist, and it's unclear at this time whether this is a FIT or an implementation issue.

      Update: appears to be an implementation issue.  I can see evidence that the implementation thinks it has removed a client from the client records (can see logging 'stopped lost cleanup process and removed client from client records'), but it actually hasn't, and the 'removed from client record' line isn't being logged.

      The impact of this should be non-existent in real-world deployments.  This only affects FIT.

      Also affecting tests like LostCleanupForSDKIntegrationRBACTest.userWithoutWritePermissionsFailsTocleanup_metadataCollection and LostCleanupForSDKIntegrationRBACTest.cleansupCollectionWithReadWritePerms_doesNotCleanupCollectionWithReadOnlyPerms.

       

      Attachments

        Activity

          People

            graham.pople Graham Pople
            graham.pople Graham Pople
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              PagerDuty