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

Received error[86] from mccouch for unknown

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Won't Fix
    • Affects Version/s: 2.0
    • Fix Version/s: 2.1.0
    • Component/s: couchbase-bucket
    • Security Level: Public
    • Labels:
      None
    • Environment:
      2.0 GA

      Description

      Seems this also exists in community:
      http://www.couchbase.com/forums/thread/high-cpu-usage-memcached-process-couchbase-2-0

      I didn't have any views, running a pure kv workload with xdcr. Currently I have 3/4 nodes in pending mode and looking in logs I see lots of 'bucket not ready' errors which may be related to these mccouch errors.

      Would be good to have resolution here esp to report back to community

      Attaching diags,

      1. diags.tar.gz
        25.35 MB
        Tommie McAfee
      No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

        Hide
        chiyoung Chiyoung Seo added a comment -

        For the bug distributions in the engine team

        Show
        chiyoung Chiyoung Seo added a comment - For the bug distributions in the engine team
        Hide
        xiaoqin Xiaoqin Ma (Inactive) added a comment -

        Can you specify the node ip what are ready and not ready?

        Show
        xiaoqin Xiaoqin Ma (Inactive) added a comment - Can you specify the node ip what are ready and not ready?
        Hide
        xiaoqin Xiaoqin Ma (Inactive) added a comment - - edited

        @Tommie McAfee

        From the log, it looks like it is always the same server gives the error message:

        [ns_server:error,2013-02-06T8:16:49.781,ns_1@10.3.121.122:ns_doctor<0.26678.1493>:ns_doctor:update_status:205]The following buckets became not ready on node 'ns_1@10.3.121.123': ["default"], those of them are active ["default"]

        Does something special happening at 10.3.121.122?

        Show
        xiaoqin Xiaoqin Ma (Inactive) added a comment - - edited @Tommie McAfee From the log, it looks like it is always the same server gives the error message: [ns_server:error,2013-02-06T8:16:49.781,ns_1@10.3.121.122:ns_doctor<0.26678.1493>:ns_doctor:update_status:205] The following buckets became not ready on node 'ns_1@10.3.121.123': ["default"] , those of them are active ["default"] Does something special happening at 10.3.121.122?
        Hide
        mikew Mike Wiederhold added a comment -

        This isn't a bug. What is happening is that couchdb is compacting the file that ep-engine is trying to write to. As a result the ep-engine write is tried 3 times and this error is logged and we requeue the items we were trying to persist. If you look in the logs you will notice that there are intervals of a few minutes between each of these messages.

        Show
        mikew Mike Wiederhold added a comment - This isn't a bug. What is happening is that couchdb is compacting the file that ep-engine is trying to write to. As a result the ep-engine write is tried 3 times and this error is logged and we requeue the items we were trying to persist. If you look in the logs you will notice that there are intervals of a few minutes between each of these messages.
        Hide
        maria Maria McDuff (Inactive) added a comment -

        NAB. by design.

        Show
        maria Maria McDuff (Inactive) added a comment - NAB. by design.

          People

          • Assignee:
            xiaoqin Xiaoqin Ma (Inactive)
            Reporter:
            tommie Tommie McAfee
          • Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Gerrit Reviews

              There are no open Gerrit changes