Couchbase Server

memcached crashed when create a default bucket in cluster

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Blocker Blocker
  • Resolution: Duplicate
  • Affects Version/s: 2.0-developer-preview-4
  • Fix Version/s: 2.0-developer-preview-4
  • Component/s: bucket-engine
  • Security Level: Public
  • Labels:
    None
  • Environment:
    windows 2008 R2 64 bit

Description

Install couchbase server 2.0.0r-590 on 6 node cluster.
Create a 6 nodes cluster without default bucket.
Then create default bucket, see 3 nodes failed.
Look at the log, see memcached crashed

Port server memcached on node 'ns_1@10.1.2.77' exited with status 255. Restarting. Messages: Trying to connect to mccouch: "localhost:11213"
Connected to mccouch: "localhost:11213"
Trying to connect to mccouch: "localhost:11213"
Connected to mccouch: "localhost:11213"
Extension support isn't implemented in this version of bucket_engine
The second phase of warmup took 21965 (us).

  7. GZip Archive
    ns-diag-20120227133236.txt.gz
    27/Feb/12 4:51 PM
    716 kB
    Thuan Nguyen

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Steve Yen added a comment -
hi bin, have you looked at this?
Show
Steve Yen added a comment - hi bin, have you looked at this?
Hide
Permalink
Bin Cui added a comment -
This problem pops up after we merged the btree-nif module. It is under investigating.
Show
Bin Cui added a comment - This problem pops up after we merged the btree-nif module. It is under investigating.
Hide
Permalink
Steve Yen added a comment -
This seems related to MB-4721
Show
Steve Yen added a comment - This seems related to MB-4721
Hide
Permalink
Steve Yen added a comment -
consider turning off NIF for windows?
Show
Steve Yen added a comment - consider turning off NIF for windows?
Hide
Permalink
Steve Yen added a comment -
not NIF -- since it's memcached crash
Show
Steve Yen added a comment - not NIF -- since it's memcached crash
Hide
Permalink
Bin Cui added a comment -
I can reproduce it on a three node cluster in ec2.
But i cannot reproduce it in a two node cluster in my dev environment.
Show
Bin Cui added a comment - I can reproduce it on a three node cluster in ec2. But i cannot reproduce it in a two node cluster in my dev environment.
Hide
Permalink
Bin Cui added a comment -
After i set up gdb and source tree to each node, i no longer can reproduce it on either ec2 and local setups. Tough!
Show
Bin Cui added a comment - After i set up gdb and source tree to each node, i no longer can reproduce it on either ec2 and local setups. Tough!
Hide
Permalink
Thuan Nguyen added a comment - - edited
I just repo this bug with build 2.0.0dp4r-717 in one node in one of our server now (IP 10.1.2.68)
Show
Thuan Nguyen added a comment - - edited I just repo this bug with build 2.0.0dp4r-717 in one node in one of our server now (IP 10.1.2.68)
Hide
Permalink
Thuan Nguyen added a comment -
I attach gdb to master node of cluster before running rebalance test on build 2.0.0dp4r-718. Memcached still scratched and gdb does not catch any error. Bin is looking on it.
Show
Thuan Nguyen added a comment - I attach gdb to master node of cluster before running rebalance test on build 2.0.0dp4r-718. Memcached still scratched and gdb does not catch any error. Bin is looking on it.
Hide
Permalink
Bin Cui added a comment -
It is essentially the same as mb-4875.
Show
Bin Cui added a comment - It is essentially the same as mb-4875.

People

  • Assignee:
    Bin Cui
    Reporter:
    Thuan Nguyen
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: