Are you doing constant writes towards the cluster, and are you sure that none of the write operations succeed? The cluster will report temp failure if it is running out of memory. In this situation your cluster need to write the items to disk before the memory may be used to store another item.. Under "normal" load the cluster is able to do this without you noticing.. (In this situation a cluster with a more small nodes would be "better" than a cluster with a few large nodes, since you would have more disks doing the persistence).
If you look at the stats in the UI you should be able to see what's going on. Cheers, Trond On Fri, Jan 3, 2014 at 4:42 PM, Thomas <[email protected]> wrote: > I have checked all three nodes but the processes seems to be running from > the time I initiated by cluster today > > Any other ideas? Is there a way to enable a more detailed log and see > where it is failing exactly? Is there a known bug of 2.1.1 community > edition? > > Thanks > > > > $> ps -eAf | grep couchbase > 218 3339 1 0 08:00 ? 00:00:00 > /opt/couchbase/lib/erlang/erts-5.8.5/bin/epmd -daemon > 218 3359 1 0 08:01 ? 00:00:10 > /opt/couchbase/lib/erlang/erts-5.8.5/bin/beam.smp -A 16 -- -root > /opt/couchbase/lib/erlang -progname erl -- -home /opt/couchbase -- -smp > enable -kernel inet_dist_listen_min 21100 inet_dist_listen_max 21299 > error_logger false -sasl sasl_error_logger false -hidden -name > [email protected] -setcookie nocookie -noshell -noinput > -noshell -noinput -run ns_babysitter_bootstrap -- -couch_ini > /opt/couchbase/etc/couchdb/default.ini > /opt/couchbase/etc/couchdb/default.d/capi.ini > /opt/couchbase/etc/couchdb/default.d/geocouch.ini > /opt/couchbase/etc/couchdb/local.ini -ns_babysitter cookiefile > "/opt/couchbase/var/lib/couchbase/couchbase-server.cookie" -ns_server > config_path "/opt/couchbase/etc/couchbase/static_config" -ns_server pidfile > "/opt/couchbase/var/lib/couchbase/couchbase-server.pid" -ns_server > cookiefile > "/opt/couchbase/var/lib/couchbase/couchbase-server.cookie-ns-server" > -ns_server enable_mlockall true > 218 3393 3359 7 08:01 ? 00:34:34 > /opt/couchbase/lib/erlang/erts-5.8.5/bin/beam.smp -A 16 -sbt u -P 327680 -K > true -MMmcs 30 -- -root /opt/couchbase/lib/erlang -progname erl -- -home > /opt/couchbase -- -smp enable -setcookie nocookie -kernel > inet_dist_listen_min 21100 inet_dist_listen_max 21299 error_logger false > -sasl sasl_error_logger false -nouser -run child_erlang child_start > ns_bootstrap -- -smp enable -kernel inet_dist_listen_min 21100 > inet_dist_listen_max 21299 error_logger false -sasl sasl_error_logger false > -couch_ini /opt/couchbase/etc/couchdb/default.ini > /opt/couchbase/etc/couchdb/default.d/capi.ini > /opt/couchbase/etc/couchdb/default.d/geocouch.ini > /opt/couchbase/etc/couchdb/local.ini -ns_babysitter cookiefile > "/opt/couchbase/var/lib/couchbase/couchbase-server.cookie" -ns_server > config_path "/opt/couchbase/etc/couchbase/static_config" -ns_server pidfile > "/opt/couchbase/var/lib/couchbase/couchbase-server.pid" -ns_server > cookiefile > "/opt/couchbase/var/lib/couchbase/couchbase-server.cookie-ns-server" > -ns_server enable_mlockall true > 218 3422 3393 0 08:01 ? 00:00:00 > /opt/couchbase/lib/erlang/lib/os_mon-2.2.7/priv/bin/memsup > 218 3423 3393 0 08:01 ? 00:00:00 > /opt/couchbase/lib/erlang/lib/os_mon-2.2.7/priv/bin/cpu_sup > 218 3425 3393 0 08:01 ? 00:00:00 > /opt/couchbase/lib/erlang/lib/ssl-4.1.6/priv/bin/ssl_esock > 218 3432 3393 0 08:01 ? 00:00:16 > /opt/couchbase/lib/ns_server/erlang/lib/ns_server/priv/i386-linux-godu > 218 3434 3359 0 08:01 ? 00:00:06 /opt/couchbase/bin/moxi -Z > port_listen=11211,default_bucket_name=default,downstream_max=1024,downstream_conn_max=4,connect_max_errors=5,connect_retry_interval=30000,connect_timeout=400,auth_timeout=100,cycle=200,downstream_conn_queue_timeout=200,downstream_timeout=5000,wait_queue_timeout=200 > -z url=http://127.0.0.1:8091/pools/default/saslBucketsStreaming -p 0 -Y y > -O stderr > 218 3435 3359 92 08:01 ? 06:54:56 > /opt/couchbase/bin/memcached -X > /opt/couchbase/lib/memcached/stdin_term_handler.so -X > /opt/couchbase/lib/memcached/file_logger.so,cyclesize=104857600;sleeptime=19;filename=/opt/couchbase/var/lib/couchbase/logs/memcached.log > -l 0.0.0.0:11210,0.0.0.0:11209:1000 -p 11210 -E > /opt/couchbase/lib/memcached/bucket_engine.so -B binary -r -c 10000 -e > admin=_admin;default_bucket_name=default;auto_create=false > > > On Friday, 3 January 2014 14:52:50 UTC+2, Thomas wrote: > >> Hi, >> >> I have been performing some tests to couchbase server 2.1.1 community >> edition and it seems that I have an issue with data insertion. I have been >> following the instructions from the following URL: http://docs.couchbase. >> com/couchbase-sdk-java-1.2/#advanced-usage >> >> The problem is that it seems that for a very large period in time (e.g. >> more than two hours) the couchbase freezes and does not accept new >> documents via the Java client (set(...)) making it problematic in data >> insertion >> >> Any ideas of why this is happening? >> >> My cluster is three nodes of 42GB memory in total and I have currently >> about 100million documents in one bucket (default) >> >> Let me know if you need any additional information, from my cluster >> >> Thanks >> > -- > You received this message because you are subscribed to the Google Groups > "Couchbase" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > -- Trond Norbye -- You received this message because you are subscribed to the Google Groups "Couchbase" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
