Uploaded image for project: 'Cassandra'
  1. Cassandra
  2. CASSANDRA-7238

Nodetool Status performance is much slower with VNodes On

Agile BoardAttach filesAttach ScreenshotBulk Copy AttachmentsBulk Move AttachmentsVotersWatch issueWatchersCreate sub-taskConvert to sub-taskMoveLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Low
    • Resolution: Fixed
    • 2.1.14, 2.2.6, 3.0.4, 3.4
    • Tool/nodetool
    • None

    • 1000 M1.Large Ubuntu 12.04

    • Low

    Description

      Nodetool status on a 1000 Node cluster without vnodes returns in several seconds. With vnodes on (256) there are OOM errors with the default XMX of 32. Adjusting the XMX to 128 allows nodetool status to complete but the execution takes roughly 10 minutes.

      Tested

      XMX    |      Status
32     |    OOM
64     |    OOM: GC Overhead
128    |    Finishes in ~10 minutes
500    |    Finishes in ~10 minutes
1000   |    Finishes in ~10 minutes

      Attachments

        Issue Links

        relates to

        Bug - A problem which impairs or prevents the functions of the product. CASSANDRA-7956 "nodetool compactionhistory" crashes because of low heap size (GC overhead limit exceeded)

        • Low -
        • Resolved

        Activity
          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            yukim Yuki Morishita Assign to me
            rspitzer Russell Spitzer
            Yuki Morishita
            Paulo Motta
            Ryan McGuire Ryan McGuire
            Votes:
            0 Vote for this issue
            Watchers:
            11 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment