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

The setup wizard defaults to "illegal" memory limit on a 32 bit process

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Critical
    • Resolution: Won't Fix
    • Affects Version/s: 1.8.0, 2.0, 2.1.0
    • Fix Version/s: 2.2.0
    • Component/s: couchbase-bucket, ns_server
    • Security Level: Public
    • Labels:
      None
    • Environment:
      box with 8GB memory
    • Link to Log File, atop/blg, CBCollectInfo, Core dump:
      somehow this thing demands some crap here

      Description

      I installed a 32 bit version of membase system on my box, and when I run the wizard it defaults to reserving more than 7GB on each node (and that doesn't work for a 32 bit process)...

      The log keeps on saying:
      =INFO REPORT==== 27-Apr-2011::09:18:31 ===
      n_0@10.0.0.3:<0.243.0>:ns_memcached:523: Changing max_size of "default" from 3210739712 to 7505707008

      =INFO REPORT==== 27-Apr-2011::09:18:41 ===
      n_0@10.0.0.3:<0.243.0>:ns_memcached:523: Changing max_size of "default" from 3210739712 to 7505707008

      =INFO REPORT==== 27-Apr-2011::09:18:51 ===
      n_0@10.0.0.3:<0.243.0>:ns_memcached:523: Changing max_size of "default" from 3210739712 to 7505707008

      32 bit systems shouldn't suggest more memory than the operating system supports per process (we could fix this by running multiple memcached processes and spread the buckets across these)

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

        Activity

        Hide
        alkondratenko Aleksey Kondratenko (Inactive) added a comment -

        we already had bug on it somewhere

        Show
        alkondratenko Aleksey Kondratenko (Inactive) added a comment - we already had bug on it somewhere
        Hide
        trond Trond Norbye added a comment -

        I guess this bug was closed due to MB-3148 , but that is a bit different.. This bug is about that the DEFAULT limit in the configuration wizard isn't a legal value. People expects to be able to just go for the default values and be able to use the system (not, accept all defaults, then have to change the configuration due to an error somewhere)

        Show
        trond Trond Norbye added a comment - I guess this bug was closed due to MB-3148 , but that is a bit different.. This bug is about that the DEFAULT limit in the configuration wizard isn't a legal value. People expects to be able to just go for the default values and be able to use the system (not, accept all defaults, then have to change the configuration due to an error somewhere)
        Hide
        alkondratenko Aleksey Kondratenko (Inactive) added a comment -

        It has been open for enough time. Worth strongly considering.

        Unfortunately it's hard to fix just from ns_server side. Or at least unclear how.

        As part of 100% proper solution:

        • we somehow need to detect that memcached is 32-bit (and in practice that means quota cannot exceed 1.9 gigs or something like that otherwise it'll overload it's memory accounting variables and assert). Note that it's perfectly fine to have 32-bit erlang managing 64-bit memcached.
        • we must not allow joining 32-bit nodes to otherwise 64-bit cluster if node quota is "high"

        I recall there was some noise caused by folks hitting similar issues on 32-bit mongo.

        Given it's unclear how we are going to fix it assigning to Ravi.

        Alternative is stop claiming with care about 32-bit (which would be reflection of reality in fact).

        Show
        alkondratenko Aleksey Kondratenko (Inactive) added a comment - It has been open for enough time. Worth strongly considering. Unfortunately it's hard to fix just from ns_server side. Or at least unclear how. As part of 100% proper solution: we somehow need to detect that memcached is 32-bit (and in practice that means quota cannot exceed 1.9 gigs or something like that otherwise it'll overload it's memory accounting variables and assert). Note that it's perfectly fine to have 32-bit erlang managing 64-bit memcached. we must not allow joining 32-bit nodes to otherwise 64-bit cluster if node quota is "high" I recall there was some noise caused by folks hitting similar issues on 32-bit mongo. Given it's unclear how we are going to fix it assigning to Ravi. Alternative is stop claiming with care about 32-bit (which would be reflection of reality in fact).
        Hide
        trond Trond Norbye added a comment -

        We do care about 32 bit windows machines. There are a lot of people in the "enterprise" world that still give their employees windows laptops that runs a 32 bit version of windows. We've seen that at different developer days etc.. As of detecting the size, just look at the stats from memcached and it'll tell you if it's 32 or 64 bit...

        Show
        trond Trond Norbye added a comment - We do care about 32 bit windows machines. There are a lot of people in the "enterprise" world that still give their employees windows laptops that runs a 32 bit version of windows. We've seen that at different developer days etc.. As of detecting the size, just look at the stats from memcached and it'll tell you if it's 32 or 64 bit...
        Hide
        siri Sriram Melkote added a comment -

        Few questions:

        (a) Is this node joining a cluster? Or is it simply a developer installing on a laptop, when they will be starting (and not joining) a cluster?

        (b) If this box has 8GB memory, it is likely 64-bit. Why do we allow running 32-bit binaries on 64-bit machines? That configuration should be disallowed in production installers.

        If we agree, I can pretty easily detect and disallow 32-bit installer on 64-bit machines.

        Show
        siri Sriram Melkote added a comment - Few questions: (a) Is this node joining a cluster? Or is it simply a developer installing on a laptop, when they will be starting (and not joining) a cluster? (b) If this box has 8GB memory, it is likely 64-bit. Why do we allow running 32-bit binaries on 64-bit machines? That configuration should be disallowed in production installers. If we agree, I can pretty easily detect and disallow 32-bit installer on 64-bit machines.
        Hide
        siri Sriram Melkote added a comment -

        Since there are no comments, I'll assume the solution to this is to detect and prevent (or at least, make it very obvious that it is a bad idea) when installing 32-bit build on 64-bit platform. (not just windows). Reassigning to Bin

        Show
        siri Sriram Melkote added a comment - Since there are no comments, I'll assume the solution to this is to detect and prevent (or at least, make it very obvious that it is a bad idea) when installing 32-bit build on 64-bit platform. (not just windows). Reassigning to Bin
        Hide
        alkondratenko Aleksey Kondratenko (Inactive) added a comment -

        my understanding is that we already prevent installing i386 packages on amd64. So we probably close this now and forget about it.

        Show
        alkondratenko Aleksey Kondratenko (Inactive) added a comment - my understanding is that we already prevent installing i386 packages on amd64. So we probably close this now and forget about it.
        Hide
        bcui Bin Cui (Inactive) added a comment -

        Yes, installer won't allow you to install a 32bit couchbase server on 64bit machine, and vice versa.

        Show
        bcui Bin Cui (Inactive) added a comment - Yes, installer won't allow you to install a 32bit couchbase server on 64bit machine, and vice versa.
        Hide
        anil Anil Kumar added a comment -

        verified on windows 7 - tried to install 64bit and installer failed with "Error: 1633 not supported .... "

        closing this bug.

        Show
        anil Anil Kumar added a comment - verified on windows 7 - tried to install 64bit and installer failed with "Error: 1633 not supported .... " closing this bug.

          People

          • Assignee:
            bcui Bin Cui (Inactive)
            Reporter:
            trond Trond Norbye
          • Votes:
            1 Vote for this issue
            Watchers:
            8 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Gerrit Reviews

              There are no open Gerrit changes