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

Increasing beam memory usage over replication on source XDCR nodes

    XMLWordPrintable

Details

    Description

      Some test details:

      2 -> 2 unidirectional replication, 25M items, ~60% resident ratio, 10K mixed front-end ops/sec.

      https://raw.github.com/pavel-paulau/perfrunner/master/tests/xdcr_2x2_unidir_25M_dgm.test

      On destination nodes memory utilization is pretty low (600-700 MB), on source node it's about 3GB and tends to grow. No surprisingly we have troubles with XDCR on Windows.

      Problem is even more noticeable in init. replication tests. RSS reaches ~5GB level. Regression is pretty obvious.

      Memory utilization becomes lower when there is no XDCR activity.

      Attachments

        1. beam.smp_rss.png
          beam.smp_rss.png
          28 kB
        2. toy_vs_2.2.0_source_nodes.pdf
          830 kB
        3. xdcr_2.5.0_856_256.pdf
          640 kB
        4. xdcr_2.5.0_856_capi.pdf
          632 kB
        5. xdcr_2.5.0_856.pdf
          622 kB
        6. xdcr_dest_220-821.pdf
          902 kB
        7. xdcr_init_source_211_vs_220.pdf
          805 kB
        8. xdcr_source_220-821.pdf
          953 kB

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. MB-9084 Source node went down multiple times after XDCR initialization [{nodedown_reason, net_tick_timeout}]

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MB-9497 Rebalance fails while loading data simultaneously onto 2 active clusters with bidirectional XDCR

          • Blocker - Blocks development and/or testing work, production could not run.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MB-9097 On a sufficiently sized cluster, seeing erl_crash dumps w/ "Cannot allocate 306104640 bytes of memory (of type "heap")"

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed
          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

              pavelpaulau Pavel Paulau (Inactive)
              pavelpaulau Pavel Paulau (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                PagerDuty