http://www.couchbase.com/issues This file is an XML representation of an issue en-us 5.2.4 845 26-12-2012 http://www.couchbase.com/issues/browse/MB-5651 Couchbase Server Build: <br/> -- 2.0.0-1351-rel <br/> <br/> Security group: <br/> -- couchbase <br/> <br/> Steps: <br/> -- create 4 nodes cluster (nodes use private ip addresses) <br/> -- create default bucket with 1 replica enabled <br/> -- insert arbitrary number of items (2M in my case) <br/> <br/> Actual result: <br/> -- no doc is replicated <br/> <br/> Notice: <br/> -- It&#39;s not about XDCR. EC2, Ubuntu 12.04 <br/> <br/> ec2-174-129-82-112.compute-1.amazonaws.com (Administrator:password, root:couchbase) MB-5651

modify ec2 security group and open traffic to/from port 11209(Replication doesn't work on EC2.)

Bug Major Resolved Fixed Public MC Brown Pavel Paulau 1.8.1-release-notes Fri, 22 Jun 2012 12:20:47 -0500 Wed, 12 Sep 2012 06:03:05 -0500 Wed, 12 Sep 2012 06:03:05 -0500 documentation 0 1 Mike, please do the initial investigation. Thanks. Ebucketmigrator is timing out while connecting to memcached. It looks like memcached might have crashed or become unresponsive after the initial vbucket creation mechanism. This appears to be the case since no longer see stats updates from ns_server in the logs. There are no crash reports from memcached though. <br/> <br/> =========================CRASH REPORT========================= <br/> &nbsp;&nbsp;crasher: <br/> &nbsp;&nbsp;&nbsp;&nbsp;initial call: ebucketmigrator_srv:init/1 <br/> &nbsp;&nbsp;&nbsp;&nbsp;pid: &lt;0.3854.0&gt; <br/> &nbsp;&nbsp;&nbsp;&nbsp;registered_name: [] <br/> &nbsp;&nbsp;&nbsp;&nbsp;exception error: no match of right hand side value {error,timeout} <br/> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;in function ebucketmigrator_srv:connect/4 <br/> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;in call from ebucketmigrator_srv:init/1 <br/> &nbsp;&nbsp;&nbsp;&nbsp;ancestors: [&#39;ns_vbm_new_sup-default&#39;,&#39;ns_memcached_sup-default&#39;, <br/> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&#39;single_bucket_sup-default&#39;,&lt;0.1187.0&gt;] <br/> &nbsp;&nbsp;&nbsp;&nbsp;messages: [] <br/> &nbsp;&nbsp;&nbsp;&nbsp;links: [#Port&lt;0.8470&gt;,&lt;0.1200.0&gt;] <br/> &nbsp;&nbsp;&nbsp;&nbsp;dictionary: [] <br/> &nbsp;&nbsp;&nbsp;&nbsp;trap_exit: false <br/> &nbsp;&nbsp;&nbsp;&nbsp;status: running <br/> &nbsp;&nbsp;&nbsp;&nbsp;heap_size: 610 <br/> &nbsp;&nbsp;&nbsp;&nbsp;stack_size: 24 <br/> &nbsp;&nbsp;&nbsp;&nbsp;reductions: 7063 <br/> &nbsp;&nbsp;neighbours: <br/> <br/> [error_logger:error] [2012-06-22 16:46:33] [<a href='mailto:ns_1@10.121.13.111'>ns_1@10.121.13.111</a>:error_logger:ale_error_logger_handler:log_report:72] Lowering priority since I don&#39;t have much information to address further. Assigning back to Pavel. Is this reproducible or do you have a cluster I can look at? @Pavel: <br/> <br/> Please put the build number on the ticket. try this cluster: <br/> <br/> ec2-174-129-98-20.compute-1.amazonaws.com <br/> ec2-23-20-111-39.compute-1.amazonaws.com <br/> ec2-23-22-235-210.compute-1.amazonaws.com <br/> ec2-107-20-81-224.compute-1.amazonaws.com The security group doesn&#39;t have port 11209 open and this port is used by ns_server for replication. Karan has just edited the security group to enable this port. I think we also should fix this: <br/> <br/> <a href="http://www.couchbase.com/docs/couchbase-manual-2.0/couchbase-network-ports.html">http://www.couchbase.com/docs/couchbase-manual-2.0/couchbase-network-ports.html</a> add port 11209 to 2.0 and 1.8 manual<br/> <a href="http://www.couchbase.com/docs/couchbase-manual-2.0/couchbase-network-ports.html">http://www.couchbase.com/docs/couchbase-manual-2.0/couchbase-network-ports.html</a> Documentation has been updated with port 11209 Date of First Response Fri, 22 Jun 2012 12:32:55 -0500 Rank 4887 Time In Status