Uploaded image for project: 'Percona Monitoring and Management'
  1. Percona Monitoring and Management
  2. PMM-2476

AWS PMM is broken on C5/M5 instances

    XMLWordPrintable

    Details

      Description

      From: Peter Zaitsev <pz@percona.com>
      Date: Wed, May 2, 2018 at 9:01 AM
      Subject: Re: AWS Marketplace install of PMM is horribly broken

      hi,

      This is very interesting....

      We actually have 16GB physical volume BUT only allocate 1GB of it to actual storage for some reason

      [root@ip-172-31-34-40 ~]# lvdisplay
      — Logical volume —
      LV Name ThinPool
      VG Name DataVG
      LV UUID dOWcIR-Yedd-CrwE-0MAd-L3vh-hoHu-9iCsh8
      LV Write Access read/write
      LV Creation host, time ip-172-30-5-239.ec2.internal, 2018-04-11 11:25:16 +0000
      LV Pool metadata ThinPool_tmeta
      LV Pool data ThinPool_tdata
      LV Status available

      1. open 2
        LV Size 15.96 GiB
        Allocated pool data 6.26%
        Allocated metadata 3.74%
        Current LE 4087
        Segments 1
        Allocation inherit
        Read ahead sectors auto
      • currently set to 8192
        Block device 253:2

      — Logical volume —
      LV Path /dev/DataVG/DataLV
      LV Name DataLV
      VG Name DataVG
      LV UUID 53GfHW-eEWn-AouA-H0Ij-aboX-514S-Ub3pLE
      LV Write Access read/write
      LV Creation host, time ip-172-30-5-239.ec2.internal, 2018-04-11 11:25:17 +0000
      LV Pool name ThinPool
      LV Status available

      1. open 1
        LV Size 1.00 GiB
        Mapped size 99.96%
        Current LE 256
        Segments 1
        Allocation inherit
        Read ahead sectors auto
      • currently set to 8192
        Block device 253:4

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                mykola.marzhan Mykola Marzhan
              • Votes:
                0 Vote for this issue
                Watchers:
                8 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 2 hours, 35 minutes
                  2h 35m