Uploaded image for project: 'MariaDB ColumnStore'
  1. MariaDB ColumnStore
  2. MCOL-715

Amazon Install - error when setting up UM storage as 'io1' volume type

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 1.0.8
    • Fix Version/s: 1.0.10, 1.1.0
    • Component/s: None
    • Labels:
    • Environment:
      aws ec2 using Columnstore AMI
    • Sprint:
      2017-14, 2017-15

      Description

      Error in postConfigure on creating a EBS volume for the UM as a type of 'io1'.

      ===== Setup Storage Configuration =====

      ----- Setup User Module MariaDB ColumnStore Data Storage Mount Configuration -----

      There are 2 options when configuring the storage: internal and external

      'internal' - This is specified when a local disk is used for the Data storage.

      'external' - This is specified when the MariaDB ColumnStore Data directory is externally mounted.

      Select the type of Data Storage [1=internal, 2=external] (1) > 2

      NOTE: The volume type. This can be gp2 for General Purpose SSD, io1 for
      Provisioned IOPS SSD, st1 for Throughput Optimized HDD, sc1 for Cold
      HDD, or standard for Magnetic volumes.

      Enter EBS Volume Type (gp2, io1, sc1, st1, standard) : (gp2) > io1

      Enter EBS Volume storage size in GB: [4,16384] (4) > 10

      Enter EBS Volume IOPS: [10,300] (unassigned) > 10

      ----- Setup Performance Module DBRoot Data Storage Mount Configuration -----

      There are 2 options when configuring the storage: internal or external

      'internal' - This is specified when a local disk is used for the DBRoot storage.
      High Availability Server Failover is not Supported in this mode

      'external' - This is specified when the DBRoot directories are mounted.
      High Availability Server Failover is Supported in this mode.

      Select the type of Data Storage [1=internal, 2=external] (1) > 2

      NOTE: The volume type. This can be gp2 for General Purpose SSD, io1 for
      Provisioned IOPS SSD, st1 for Throughput Optimized HDD, sc1 for Cold
      HDD, or standard for Magnetic volumes.

      Enter EBS Volume Type (gp2, io1, sc1, st1, standard) : (gp2) > io1

      Enter EBS Volume storage size in GB: [4,16384] (4) > 100

      Enter EBS Volume IOPS: [100,3000] (3000) >

      ===== Setup Memory Configuration =====

      NOTE: Setting 'NumBlocksPct' to 70%
      Setting 'TotalUmMemory' to 50%

      ===== Setup the Module Configuration =====

      Amazon Install: For Module Configuration, you have the option to provide the
      existing Instance IDs or have the Instances created.
      You will be prompted during the Module Configuration setup section.

      ----- User Module Configuration -----

      Enter number of User Modules [1,1024] (1) >

          • User Module #1 Configuration ***

      Create Instance for um1 [y,n] >

      Launched Instance for um1: i-069c481dd93d4f4c3
      Getting Private IP Address for Instance i-069c481dd93d4f4c3, please wait...
      Private IP Address of i-069c481dd93d4f4c3 is 172.30.0.206

      Create an EBS volume for um1 ? [y,n] >
      Create AWS Volume for UM #1

      invalid literal for int() with base 10: 'unassigned'

      invalid literal for int() with base 10: 'unassigned'

      invalid literal for int() with base 10: 'unassigned'

      invalid literal for int() with base 10: 'unassigned'

      invalid literal for int() with base 10: 'unassigned'

          • ERROR: Failed to create a Volume for um1 1
            ERROR: volume create failed for um1

        Attachments

          Activity

            People

            Assignee:
            hill David Hill (Inactive)
            Reporter:
            hill David Hill (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.