Details

    • Type: Improvement
    • Status: Closed
    • Priority: Critical
    • Resolution: Done
    • Affects Version/s: 2.0, 2.1.1, 2.2.0, 2.5.0
    • Fix Version/s: techdebt-backlog
    • Component/s: None
    • Security Level: Public

      Description

      Page here: http://www.couchbase.com/docs/couchbase-manual-2.0/best-practice-guide.html

      Can we please add:
      -We recommend a minimum of 3 nodes in any production deployment. This is so that auto-failover can be enabled, that you don't have a single point of failure should one node go down, if one node does go down the load of restoring that node is shared by 2 instead of 1, and so that the need for growth can be spread by 3 servers instead of just two and online upgrades can be performed without bringing the cluster down to one node.
      -We recommend (and in fact enforce) no more than 10 buckets per cluster due to resource requirements.
      -A link to the View writing best practices
      -We recommend separating the disk paths of config files, data files and index files.

      This would also be a great page to have a set of "added" reading at the top:
      -Perry's rebalance blog
      -Perry's sizing blog
      -Architectural whitepaper
      -Link to our "learn" section for more content

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

        Activity

        Hide
        kzeller kzeller added a comment -

        Meeting with Anil on Reorganization: 7/6/2013

        -Should carve out Best practices as standalone guide from Manual, Right now too buried, does not address all topis we need.
        -Best Practice: for every major feature, have a section called Best Practice, e.g. "XDCR Best Practices"
        -On downloads webpage have link to downloadable Best practices PDF.

        Meeting with Anil and Dipti 7/5/2013
        -To discuss with Wayne: have meeting with 1-2 QA people + Support and do info sessions. Docs to based content on these info sessions.

        Show
        kzeller kzeller added a comment - Meeting with Anil on Reorganization: 7/6/2013 -Should carve out Best practices as standalone guide from Manual, Right now too buried, does not address all topis we need. -Best Practice: for every major feature, have a section called Best Practice, e.g. "XDCR Best Practices" -On downloads webpage have link to downloadable Best practices PDF. Meeting with Anil and Dipti 7/5/2013 -To discuss with Wayne: have meeting with 1-2 QA people + Support and do info sessions. Docs to based content on these info sessions.
        Hide
        anil Anil Kumar added a comment -

        This will be only in 3.0 and above documentation we don't need to back port to older versions.

        Show
        anil Anil Kumar added a comment - This will be only in 3.0 and above documentation we don't need to back port to older versions.
        Hide
        akurtzman Amy Kurtzman added a comment -

        This is the current link to the best practices page that is mentioned in the first line of the description: http://docs.couchbase.com/couchbase-manual-2.0/#best-practices.

        It looks like some of this information got moved to Deployment considerations in 3.0 at http://docs.couchbase.com/admin/admin/Concepts/bp-deployment-considerations.html

        Show
        akurtzman Amy Kurtzman added a comment - This is the current link to the best practices page that is mentioned in the first line of the description: http://docs.couchbase.com/couchbase-manual-2.0/#best-practices . It looks like some of this information got moved to Deployment considerations in 3.0 at http://docs.couchbase.com/admin/admin/Concepts/bp-deployment-considerations.html

          People

          • Assignee:
            ruth Ruth Harris
            Reporter:
            perry Perry Krug
          • Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Gerrit Reviews

              There are no open Gerrit changes