Uploaded image for project: 'Couchbase Server'
  1. Couchbase Server
  2. MB-4600

server goes unavailable, protocol violations after a period of time

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Critical
    • Resolution: Incomplete
    • Affects Version/s: 2.0-developer-preview-3
    • Fix Version/s: 2.0-developer-preview-4
    • Component/s: None
    • Security Level: Public
    • Labels:
      None
    • Environment:
      - We only have 1 node (4GB of RAM) and 1 bucket ('default' bucket)
      - We run Couchbase 2.0 Dev Preview 3
      - The server is homed in a large Amazon EC2 instance (2 virtuals cores)

      Description

      See full description at
      http://www.couchbase.org/forums/thread/node-down-impossible-get-it-back

      Summary is that after some time under regular workload, the end user sees a protocol violation via the Ruby Client and sees in the log that it the bucket was shutdown and did not restart.

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

        Activity

        Hide
        filipe manana filipe manana added a comment -

        This seems to be related to the cross data center replication code:

        {log_info,ns_server,error,xdc_rep_manager,handle_info,263,

        Ask Srini, I'm not familiar with its implementation neither have the time to do it.

        Show
        filipe manana filipe manana added a comment - This seems to be related to the cross data center replication code: {log_info,ns_server,error,xdc_rep_manager,handle_info,263, Ask Srini, I'm not familiar with its implementation neither have the time to do it.
        Hide
        alkondratenko Aleksey Kondratenko (Inactive) added a comment -

        xdc replication manager issues are unrelated. This think always crashes when we shutdown.

        Here's what looks like real issue in couch:

        [error_logger:error] [2011-12-23 10:18:07] [ns_1@127.0.0.1:error_logger:ale_error_logger_handler:log_msg:76] Error in process <0.16293.9> on node 'ns_1@127.0.0.1' with exit value: badmatch,{ok,<<295271 bytes>>,[

        {couch_file,read_raw_iolist_int,3}

        ,

        {couch_file,maybe_read_more_iolist,4}

        ,

        {couch_file,reader_loop,1}

        ]}

        Show
        alkondratenko Aleksey Kondratenko (Inactive) added a comment - xdc replication manager issues are unrelated. This think always crashes when we shutdown. Here's what looks like real issue in couch: [error_logger:error] [2011-12-23 10:18:07] [ns_1@127.0.0.1:error_logger:ale_error_logger_handler:log_msg:76] Error in process <0.16293.9> on node 'ns_1@127.0.0.1' with exit value: badmatch,{ok,<<295271 bytes>> ,[ {couch_file,read_raw_iolist_int,3} , {couch_file,maybe_read_more_iolist,4} , {couch_file,reader_loop,1} ]}
        Hide
        steve Steve Yen added a comment -

        Hi Aliaksey, does this need reassignment?

        Show
        steve Steve Yen added a comment - Hi Aliaksey, does this need reassignment?
        Hide
        steve Steve Yen added a comment -

        alk is impacted – reassigning to aliaksey a. to help

        Show
        steve Steve Yen added a comment - alk is impacted – reassigning to aliaksey a. to help
        Hide
        steve Steve Yen added a comment -

        need more diag from servers

        Show
        steve Steve Yen added a comment - need more diag from servers

          People

          • Assignee:
            Aliaksey Artamonau Aliaksey Artamonau
            Reporter:
            ingenthr Matt Ingenthron
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Gerrit Reviews

              There are no open Gerrit changes