memcached - Couchbase temporary failure -
memcached - Couchbase temporary failure -
i'm using couchbase 2.0.1 , using:
operationfuture<boolean> set = client.set(keysesioncanal, 0, sesioncanal, couchdbclient.transcoder_sesion_canal); logger.info( set.getstatus().getmessage() ); sometimes error message: temporary failure
i'm pretty new using couchbase , i'm not sure happening. in couchbase logs can see lot of messages as: "total memory utilize reached low water mark, stop warmup"
could cause?
another weird log me is: " sending tap_opaque command "opaque_enable_auto_nack" , vbucket 0" " tap (producer) eq_tapq:replication_ns_1@x.x.x.x - suspend 5.00 secs"
what meaning of this? can find documentation about?
this happening hitting limits of amount of memory available caching. cluster effort free memory (by ejecting not-recently-used items ram) if writing info fast cluster free memory before reaches high watermark, may see tempfail errors - indicate client should off , retry. covered server-side in ejection, eviction , working-set managerment.
exactly how handle depends on specific sdk using, general info available under handling temporary out-of-memory errors in developer guide.
note low/high watermark algorithm improved in subsequent releases may have improve experience latest release (2.0.1 quite old now).
memcached couchbase
Comments
Post a Comment