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

[2.0.1 RN] More 2.0.1 changes in cbepctl

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.0.1
    • Fix Version/s: 2.0.1
    • Component/s: None
    • Security Level: Public
    • Flagged:
      Release Note

      Description

      Great point. I will work with Karen making sure all is captured in right docc for wide audience.

      Thanks,
      Jin

      On Jan 14, 2013, at 4:07 PM, Steve Yen wrote:

      Thanks Jin,
      If not already, this seems like it should be documented somewhere (or existing docs updated) so that all the downstream folk (QE, techdocs, support) can benefit?
      Cheers,
      Steve
      ________________________________________
      From: Jin Lim
      Sent: Monday, January 14, 2013 3:14 PM
      To: Ronnie Sun
      Cc: Mike Wiederhold; Chiyoung Seo; Steve Yen; Ketaki Gangal; Farshid Ghods
      Subject: Re: water mark changes
      Hi Ronnie,
      All three parameters now can be changed during run tim via cpepctl.
      mem_high_wat
      mem_low_wat
      mutation_mem_threshold (temp_oom)
      Thanks,
      Jin
      On Jan 14, 2013, at 2:13 PM, Ronnie Sun wrote:
      Hi Mike, Chiyoung,
      Do the recent water mark changes leave tmp_oom configurable too?
      Ronnie

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

        Activity

        Hide
        kzeller kzeller added a comment -

        Hi Jin,

        Can you clarify:

        In the past you could not update these settings while a node is online and now you can?

        Please also provide three examples including bucket info in needed for the new parameters.

        Thanks!

        Show
        kzeller kzeller added a comment - Hi Jin, Can you clarify: In the past you could not update these settings while a node is online and now you can? Please also provide three examples including bucket info in needed for the new parameters. Thanks!
        Hide
        mikew Mike Wiederhold added a comment -

        mutation_mem_threshold is the only new stat and works the same as the other two which should already be in your documentation. Can you check to see if you already have mem_high_wat and mem_low_wat documented. If not please assign this to me and I will provide examples.

        Show
        mikew Mike Wiederhold added a comment - mutation_mem_threshold is the only new stat and works the same as the other two which should already be in your documentation. Can you check to see if you already have mem_high_wat and mem_low_wat documented. If not please assign this to me and I will provide examples.
        Hide
        mikew Mike Wiederhold added a comment -

        mutation_mem_threshold is the amount of memory that can be used before the client starts receiving the temp oom message.

        Show
        mikew Mike Wiederhold added a comment - mutation_mem_threshold is the amount of memory that can be used before the client starts receiving the temp oom message.
        Hide
        jin Jin Lim (Inactive) added a comment -

        Thanks Mike for detailed explanation.

        ex:
        password is only required for SASL authenticating bucket and default bucket name is "default"
        ./cbepctl 10.5.2.31:11210 -b bucket_name -p password set flush_param mem_high_wat 70
        ./cbepctl 10.5.2.31:11210 -b bucket_name -p password set flush_param mem_low_wat 60
        ./cbepctl 10.5.2.31:11210 -b bucket_name -p password set flush_param mutation_mem_threshold 65

        Show
        jin Jin Lim (Inactive) added a comment - Thanks Mike for detailed explanation. ex: password is only required for SASL authenticating bucket and default bucket name is "default" ./cbepctl 10.5.2.31:11210 -b bucket_name -p password set flush_param mem_high_wat 70 ./cbepctl 10.5.2.31:11210 -b bucket_name -p password set flush_param mem_low_wat 60 ./cbepctl 10.5.2.31:11210 -b bucket_name -p password set flush_param mutation_mem_threshold 65
        Hide
        kzeller kzeller added a comment -

        I've already got the high water and low water documented.

        For this new one mutation_mem_threshold, do you have guideance on when customers should change this and when not to change this?

        Also, does changing this setting impact other parts of server operation or client/server ops that people should be aware of (e.g warmup) What will they observe and should observe if they change it?

        Please add and assign back.

        Karen

        Show
        kzeller kzeller added a comment - I've already got the high water and low water documented. For this new one mutation_mem_threshold, do you have guideance on when customers should change this and when not to change this? Also, does changing this setting impact other parts of server operation or client/server ops that people should be aware of (e.g warmup) What will they observe and should observe if they change it? Please add and assign back. Karen
        Hide
        kzeller kzeller added a comment -

        P.S. I'm thinking this impacts ejection, yes?

        Show
        kzeller kzeller added a comment - P.S. I'm thinking this impacts ejection, yes?
        Hide
        mikew Mike Wiederhold added a comment -

        This impacts when you start receiving tmp oom messages on in your client application. By default this value is now when memory is 95% full and this leaves 5% of your memory for overhead. I would only recommend people changing this value (higher) if they have a lot of memory or (lower) if they think they need more space for the overhead, like data structures and disk queues, of Couchbase.

        Show
        mikew Mike Wiederhold added a comment - This impacts when you start receiving tmp oom messages on in your client application. By default this value is now when memory is 95% full and this leaves 5% of your memory for overhead. I would only recommend people changing this value (higher) if they have a lot of memory or (lower) if they think they need more space for the overhead, like data structures and disk queues, of Couchbase.
        Hide
        kzeller kzeller added a comment -

        Ok Added to RN 2.0.1: There is a new setting available in <command>cbepctl</command> named <command>mutation_mem_threshold</command>. This is the
        amount of RAM that can be used on the server before a client begins receiving temporary out of
        memory errors. For more information, see <xref linkend="couchbase-admin-cbepctl-mutation_mem" />.

        And then cross ref to new section:

        Changing Setting for Out Of Memory Errors

        By default, Couchbase Server will send clients a temporary out of memory error if RAM is 95% consumed and only 5% RAM remains for overhead. We do not suggest you change this default to a higher value; however you may choose to reduce this value if you think you need more RAM available for system overhead such as disk queue or for server data structures. To change this value:

        shell>./cbepctl 10.5.2.31:11210 -b bucket_name -p password set flush_param mutation_mem_threshold 65

        In this example we reduce the threshold to 65% of RAM. This setting must be updated on a per-node, per-bucket basis, meaning you need to provide the specific node and named bucket to update this setting. To update it for an entire cluster, you will need to issue the command for every combination of node and named bucket that exists in the cluster.

        Show
        kzeller kzeller added a comment - Ok Added to RN 2.0.1: There is a new setting available in <command>cbepctl</command> named <command>mutation_mem_threshold</command>. This is the amount of RAM that can be used on the server before a client begins receiving temporary out of memory errors. For more information, see <xref linkend="couchbase-admin-cbepctl-mutation_mem" />. And then cross ref to new section: Changing Setting for Out Of Memory Errors By default, Couchbase Server will send clients a temporary out of memory error if RAM is 95% consumed and only 5% RAM remains for overhead. We do not suggest you change this default to a higher value; however you may choose to reduce this value if you think you need more RAM available for system overhead such as disk queue or for server data structures. To change this value: shell>./cbepctl 10.5.2.31:11210 -b bucket_name -p password set flush_param mutation_mem_threshold 65 In this example we reduce the threshold to 65% of RAM. This setting must be updated on a per-node, per-bucket basis, meaning you need to provide the specific node and named bucket to update this setting. To update it for an entire cluster, you will need to issue the command for every combination of node and named bucket that exists in the cluster.
        Hide
        kzeller kzeller added a comment -

        Ok Added to RN 2.0.1: There is a new setting available in <command>cbepctl</command> named <command>mutation_mem_threshold</command>. This is the
        amount of RAM that can be used on the server before a client begins receiving temporary out of
        memory errors. For more information, see <xref linkend="couchbase-admin-cbepctl-mutation_mem" />.

        And then cross ref to new section:

        Changing Setting for Out Of Memory Errors

        By default, Couchbase Server will send clients a temporary out of memory error if RAM is 95% consumed and only 5% RAM remains for overhead. We do not suggest you change this default to a higher value; however you may choose to reduce this value if you think you need more RAM available for system overhead such as disk queue or for server data structures. To change this value:

        shell>./cbepctl 10.5.2.31:11210 -b bucket_name -p password set flush_param mutation_mem_threshold 65

        In this example we reduce the threshold to 65% of RAM. This setting must be updated on a per-node, per-bucket basis, meaning you need to provide the specific node and named bucket to update this setting. To update it for an entire cluster, you will need to issue the command for every combination of node and named bucket that exists in the cluster.

        Show
        kzeller kzeller added a comment - Ok Added to RN 2.0.1: There is a new setting available in <command>cbepctl</command> named <command>mutation_mem_threshold</command>. This is the amount of RAM that can be used on the server before a client begins receiving temporary out of memory errors. For more information, see <xref linkend="couchbase-admin-cbepctl-mutation_mem" />. And then cross ref to new section: Changing Setting for Out Of Memory Errors By default, Couchbase Server will send clients a temporary out of memory error if RAM is 95% consumed and only 5% RAM remains for overhead. We do not suggest you change this default to a higher value; however you may choose to reduce this value if you think you need more RAM available for system overhead such as disk queue or for server data structures. To change this value: shell>./cbepctl 10.5.2.31:11210 -b bucket_name -p password set flush_param mutation_mem_threshold 65 In this example we reduce the threshold to 65% of RAM. This setting must be updated on a per-node, per-bucket basis, meaning you need to provide the specific node and named bucket to update this setting. To update it for an entire cluster, you will need to issue the command for every combination of node and named bucket that exists in the cluster.

          People

          • Assignee:
            kzeller kzeller
            Reporter:
            kzeller kzeller
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Gerrit Reviews

              There are no open Gerrit changes