Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 1.2.0
    • Fix Version/s: None
    • Component/s: library
    • Security Level: Public
    • Labels:
      None
    • Environment:
      Ubuntu 12.04 64-bit

      Description

      I'm trying to use txcouchbase and I'm getting this error:

      	    data = yield self.cb.get(num)
      	  File "/home/joe/foo/src/couchbase/txcouchbase/connection.py", line 295, in ret
      	    return self._wrap(meth, *args, **kwargs)
      	  File "/home/joe/foo/src/couchbase/txcouchbase/connection.py", line 288, in _wrap
      	    opres = meth(self, *args, **kwargs)
      	  File "/home/joe/foo/src/couchbase/couchbase/connection.py", line 489, in get
      	    return _Base.get(self, key, ttl, quiet, replica, no_format)
      	couchbase.exceptions.ClientTemporaryFailError: <RC=0x1B[Temporary failure on the client. Try again later], There was a problem scheduling your request, or determining the appropriate server or vBucket for the key(s) requested. This may also be a bug in the SDK if there are no network issues., C Source=(src/get.c,335)>
      
      

      Any ideas?

      No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

        Hide
        mnunberg Mark Nunberg added a comment -

        I think we resolved this?

        Show
        mnunberg Mark Nunberg added a comment - I think we resolved this?
        Hide
        joehillen Joe Hillenbrand added a comment -

        Sure. I think the original problem was that my bucket name had extra quotes in it, but the strange part was that it wasn't an error on connection but an error when trying to do a query.

        I think an actual fix would be to raise an error when there is an invalid bucket when connecting.

        Show
        joehillen Joe Hillenbrand added a comment - Sure. I think the original problem was that my bucket name had extra quotes in it, but the strange part was that it wasn't an error on connection but an error when trying to do a query. I think an actual fix would be to raise an error when there is an invalid bucket when connecting.

          People

          • Assignee:
            mnunberg Mark Nunberg
            Reporter:
            joehillen Joe Hillenbrand
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Gerrit Reviews

              There are no open Gerrit changes