Uploaded image for project: 'Spymemcached Java Client'
  1. Spymemcached Java Client
  2. SPY-134

error in timeout log message

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Major
    • 2.11.3
    • None
    • None
    • Security Level: Public
    • None

    Description

      In analyzing a log just now, I saw:

      net.spy.memcached.OperationTimeoutException: Timeout waiting for value: waited 10,000 ms. Node status: Connection Status

      { 10.90.76.179/10.90.76.179:11210 active: true, authed: true, last read: 4,219,716 ms ago 10.90.76.178/10.90.76.178:11210 active: true, authed: true, last read: 1,157,373 ms ago }

      Those "last read" seem wrong. These should be fixed.

      Attachments

        For Gerrit Dashboard: SPY-134
        # Subject Branch Project Status CR V
        37646,2 SPY-134: Make sure lastReadTimestamp is concurrency safe. master spymemcached Status: MERGED +2 +1

        Activity

          People

            daschl Michael Nitschinger
            ingenthr Matt Ingenthron
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Gerrit Reviews

                There are no open Gerrit changes

                PagerDuty